Trouble in Mountain Lion

[tamaracks]

Hi,

I see that there are other posts about trouble with Mountain Lion, but the details seem to vary widely, so I wondered if anyone had seen the behavior I have and successfully gotten it to work.

I mainly use QuickCursor to edit text from Chrome in Byword. When I invoke my keyboard shortcut while i

[tamaracks]

Accidentally submitted too soon.

When I invoke the keyboard shortcut, everything seems to proceed normally until I finish typing and close the window. A document is opened in Byword with a title that matches the title of the tab in Chrome. Any text from the box in Chrome is placed in the document. But when I close the window, nothing happens except that the window is closed. The text is not sent back to Chrome. Fortunately, it does save the file so I can reopen it and copy and paste.

I would appreciate any information anyone has that could make QC workable in some manner.

Thanks,

Tamara

[Grey]

Could you give me some example sites I could test on? For the couple of text fields I just tested in Chrome, QC seemed to paste back to Byword OK (old-style Gmail compose window, text boxes on GitHub.com for example).

QC will lose its place if the tabs are changed in Chrome, though. I'm also using Byword already-launched with no windows open and the iCloud/On My Mac open document dialog closed too.

--
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/-/7jR49pOBLAUJ.
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.

[Tamara Ng]

Hi Grey,

I suspect that it may be some kind of config or support file issue, rather than related to the particular web site. I tried a few more things, and it's now working. I'll outline what I tried in case it helps anyone else.

QuickCursor works fine on my MacBook Air, which has been running Mountain Lion for a while. I did an upgrade install from Lion to Mountain Lion on the laptop shortly after ML was released. QuickCursor was installed before that upgrade, and has continued to work fine on the MBA.

The Mac I was having trouble on is a recently purchased Mac mini, which was migrated from an older iMac that had been running Lion. QuickCursor worked fine in Lion on the iMac, but since migrating, it's been behaving as I described.

After reading your message, I first tried quitting QC, copying the plist file from the MBA to the mini, and relaunching QC, but there was no change in behavior. I also tried quitting, deleting the plist file from the mini, and relaunching, but that also made no difference.

Next, I tried deleting the application and plist file and reinstalling it from the App Store. That also did not change anything. (I installed the app from a different account, because we keep our regular accounts as non-admin on this Mac, and have a separate admin account, which is where I installed the app. On the laptop, for convenience, I've used my normal account as an admin account.) However it still made no change when I logged back into my account.

The last thing I tried was to change my user account to an admin user. In order to do that, I had to reboot the Mac. After logging back in as me as an admin, I was able to get QuickCursor to work successfully. One other thing that changed at the same time was that when I logged out of my account before changing it to admin, I had inadvertently not checked the option to restore windows when logging back in. So it was either changing to an admin user that got things to work, or it was resetting my window state.

I think it was more likely changing my user to admin, because I think I must have reset the window state at some other point between migrating to the mini and now, but I can't be sure.

After I got QC working, I logged out again and changed my user back to non-admin, rebooted again, then logged back in as me. QC continued to work, even though I was no longer an admin user.

So, beats me what happened to break it, but I'm glad I got it working!

Thanks,

Tamara

[Grey]

Wow, that's a nice bit of work. I'll see if I can trace backwards through your steps and see if I can get QC non-functional by going in reverse. Either way, thanks for the update and glad to hear QC is working for you again.

[Daniel Shannon]

Dear Grey,

After reading Tamara's posts, I decided to see if I couldn't reproduce her success. My problem was that QuickCursor, which I've been using with Sublime, seemed to work fine for a time, but then suddenly stopped responding to my keyboard shortcut. Whether it would have responded to GUI input I don't know, because I couldn't get it to show up in Bartender and so had to kill it. After killing it, I trashed the preferences, restarted QC, reconfigured, and restarted again; it then would respond to the shortcut and switch to Sublime, but without opening a file. I tried quitting Mail and Safari without saving their window states, but the same thing happened when I opened them again. So I rebooted, making sure to uncheck the restore-windows option, and now it's running fine.

Does QuickCursor keep a log anywhere that would help you get to the bottom of this? Thanks for looking into it!

Best,

Daniel

[Grey]

QC is relatively verbose in Console.app, it can be outputting a number of messages per operation.

By 'saving window states', do you mean OS X Resume or something different via Bartender?

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

[Daniel Shannon]

Sorry to have been unclear—I meant OS X Resume. I just tried to fire it again from this text box and experienced the same behavior as before: Sublime gets focus, but no new file is opened; then, after a couple of attempts, QuickCursor quits. I couldn't find anything in the console, either searching for "Quick" or skimming recent messages.

[Grey]

Below is what I just posted to another thread. In summary, there IS a method for workaround to prevent QC from getting caught by sandboxing quarantine (at least I think that's what's going on), but it's unacceptable for a paid app. We're removing QC from sale, and please contact the App Store support team about a refund.

Here's what I've found with iA Writer under 10.8: The new 10.8 Open/New Document dialog box (with the iCloud/On My Mac options) is a major point of conflict. QC can't force Writer to create a new document from it or even dismiss it, and then the OS X sandbox seems to kick in (this is my guess) and quarantine QC for trying to open/work in another app's sandbox container. I'm not 100% sure that's what's going on, but it's the scenario I have so far.

The nasty part is that the sandbox seems to maintain the quarantine state until the next user session (it's apparently released after a log out/log in).

Here's what's working for me with iA Writer and other App Store sandboxed apps:

1. Launch the editor app first (iA Writer in this case). Having QC launch a sandboxed app will immediately quarantine QC, apparently.

2. Dismiss the "new document/open document" dialog if it pops up.

3. For iA Writer only, Byword doesn't seem to care: Open a new blank document (maybe you don't need to, Byword seems OK but Writer throws a fit sometimes and re-invokes the New/Open dialog box instead).

Like I said, that stinks and it's not good enough. I'm sorry for the very poor experience and please ask the App Store for a refund immediately. We're removing QC from sale in the Mac App Store effective today.

The source code to QuickCursor is posted here: https://github.com/jessegrosjean/quickcursor

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