Thursday, January 09, 2014

Finally, an Intractable Problem in Chrome


The Chromebox/Chromebook are kind of like Macs in the sense that most stuff just ... works. If you use Windoze, you're used to weird error messages and inexplicable system crashes. That stuff just doesn't happen much on Mac, nor in ChromeOS.

But, finally, more than a year in the ChromeOS world, I've run into a problem that doesn't seem to want to fix:

For quite some time, I've used a text editor called Sourcekit (in conjunction with Writebox -- that way I can have two editors open at once, which I need for certain things). One important feature of Sourcekit is that I can load/save files directly from and to Dropbox. But starting the other day, I get re-authorization requests to connect Sourcekit/Dropbox, and when I approve, nothing happens. I just get a blank tab, and the next time I open Sourcekit, I get the request again.

Writebox also integrates with Dropbox and is working just fine. But I tried out another app, Writekit, and got the same error (yes, I've noticed the kit/box/write ubiquity). So I'm thinking the problem is probably at Dropbox, not with Chrome/ChromeOS per se. Or maybe it's with my Chromebox in particular (haven't used the Chromebook recently); I think that may be the case because I haven't seen any recent panicked "why can't I ..." threads on the web about the problem.

Fortunately, there's an easy work-around -- I installed yet another text editor, Caret. It isn't integrated with Dropbox, which means there's some extra futzing around, but it gets the job done.
Enhanced by Zemanta

blog comments powered by Disqus
Three Column Modification courtesy of The Blogger Guide
Some graphics and styles ported from a previous theme by Jenny Giannopoulou