QuickCursor has been removed from sale due to ongoing sandbox conflicts.

[Grey]

As of today (11 December 2012), I have removed QuickCursor from sale
in the Mac App Store. This means that the app's binary is still in the
App Store (you should be able to re-download it if you purchased it),
but no new purchases can be made.

Due to an increasing number of problems with OS X sandboxing,
QuickCursor doesn't always work as it should with the apps it's
supposed to be compatible with, and inconsistently for many. What
works for one person doesn't for another, and it's not clear why.

If you recently purchased a copy of QuickCursor, please contact the
Mac App Store's support team about a refund. You deserve a working app
without a whole lot of workarounds, and I'm not confident we can find
a solution that will get approved in the App Store at this point.

I'm sorry about this, and I apologize for not being able to deliver an
update to fix all the running issues within a reasonable amount of
time.

QuickCursor's source code can be found here: https://github.com/jessegrosjean/quickcursor

[Erik Price]

I've used QC for several years and it's been immensely helpful. Having recently migrated to a new computer a few weeks back, I went to download it again from the web site and saw that the binary was not being distributed there anymore. I was only too happy to buy it for the paltry $4.99 from the MAS instead, in gratitude for having been able to use this software for free all this time. Of course, I'm also one of the folks who can't get QC to work anymore. I'm fine with requesting a refund if you think that doing so would somehow communicate to Apple that sandboxing is not an adequate solution for all apps in the App Store. But if that's really just wasting everyone's time, I don't want my money back; you earned it.

That said, do I need to remove/change anything in the source code on GitHub in order to get QC working again (presumably without the problematic sandboxing code enabled)?

e

[Grey]

Thanks for the kind words, I believe QC's declining functionality and reliability was *also* an issue with the other sandboxed apps and how OS X has developed through 10.7 and 10.8. For example, QC as-is should work fine with, say, TextWrangler as downloaded from the Bare Bones website. But getting it to work reliably with a sandboxed app like iA Writer is a bit of a tricky dance, where a misstep seems to result in QC getting quarrantined by OS X until the next user session (log out/log in again). 

I don't believe QC's GitHub code even *has* sandboxing enabled, so even debug builds without codesigning or entitlement files work about as well for me as the MAS download did (meaning, not so much).

Please DO build a copy for yourself from the source! As far as I can tell, though, stripping QuickCursor of all the little MAS references here and there won't make it a fully functional app again under 10.7/10.8. So far, that's why I haven't made a build available from the Hog Bay website -- it goes beyond simply taking the app off the App Store.

--
You received this message because you are subscribed to the Google Groups "QuickCursor" group.
To view this discussion on the web visit https://groups.google.com/d/msg/quickcursor/-/BqDRdIse-SAJ.
To post to this group, send email to quick...@googlegroups.com.
To unsubscribe from this group, send email to quickcursor...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/quickcursor?hl=en.

[Erik Price]

I tried it, but as you predicted, I get the same problems that I get from the MAS version: the MacVim window which opens does not contain the text I'm editing in the original application, and I get a spinning beach ball when I mouse over the QC status item. From your description of the problem, it seems odd, since MacVim isn't an app from the MAS (so I would assume it doesn't have the same sandbox limitations), but I'm not qualified to speculate on what might not be working. Thanks again for the past several years of creating and maintaining a great tool.

e

[Grey]

Yeah, MacVim's another weird case. It almost always works fine for me, therefore not sure about why there's an inconsistency between people's experiences. Even comparing .vimrc files hasn't turned up much difference in the past. If you'd like, feel free to send your .vimrc file my way (grey at hogbaysoftware.com) and I'll take a look vs my own. Probably no real difference, but hey :-)

To view this discussion on the web visit https://groups.google.com/d/msg/quickcursor/-/utrhgI75CY4J.

[mon...@gmail.com]

Workaround for MacVim: 

Highlight (select) the text in your application of choice before you invoke QC. 

When done editing in MacVim, save and close the buffer.

Hope this helps you.

mon10a