Re: [QuickCursor] Re: Problem: Upon pressing Command-W, save dialog box comes up.

[Grey]

I'll take a closer look once I'm back from the weekend. Any difference if you already have WriteRoom open before invoking QC?

10.8's aggressive sandboxing and a few other changes in action, perhaps.

On Sep 22, 2012, at 12:03 PM, Devin Beecher <dgbe...@gmail.com> wrote:

It broke again this morning, while using it to edit text in Notational Velocity. I had used Notational Velocity's built-in "Edit With" feature, which does the same thing as QuickCursor but with a bit of added functionality. Right after this, I started to have the same problem as before with QuickCursor. Interestingly, reinstalling QuickCursor did not fix the problem, but reinstalling WriteRoom did. I've not been able to replicate the problem since then, even after fiddling again with Notational Velocity's "Edit With" feature.

This system feels very fragile to me.

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

[Grey]

Let's see if this is specifically a sandbox issue. Try this: Download the website's version of WriteRoom and replace the App Store WriteRoom.app with that. Then try QC; if it's *not* a sandboxing issue, then in theory WR should open properly when invoked via QC.

The sandboxing problem should be generally solved by having the editor app already launched, so what you describe might be bit outside of that known case.

Another approach: In QC's preferences, try adding the source app's name to the Temporary File Extensions list, and an extension of 'txt'. I've run into some 10.8 sandbox permissions without extensionless files (ie, snagging text from Mail.app) and that seemed to solve it for me.

Last: Could you open Console.app, try running QC, and let me know what the console spits out related to the source app, editor app, or QC? Thanks!

10.8 + sandboxing is a bit of a brick wall we keep running into, sorry

On Saturday, September 22, 2012 at 8:41 PM, Devin Beecher wrote:

Thanks for the reply!

If QuickCursor and WriteRoom are working, then they work whether WR is open or closed. If QC/WR are broken, then they don't work whether WR is open or closed. Furthermore, the "breaking" has happened both when WR was open -- as it broke this morning while editing from Notational Velocity -- and also when WR was closed -- as it broke just now while trying to write an email from Mail. 

I haven't been able to fix it this last time. Reinstalling both apps sequentially did not help. Maybe I have to reinstall them simultaneously, or restart a few extra times ... but it feels like something deeper is wrong, and reinstalling once again isn't going to fix it permanently ... I'll wait to hear from you after the weekend. Thanks for your efforts!

Devin

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

[Grey]

Alright, more fodder for the bug report. This looks different than what I'd seen on another issue with MacVim. The console output doesn't look like an immediate cause for what you're seeing but it's all helpful. Thanks.

When you invoked QC from Notational Velocity, was it in a blank/untitled document or an already existing document? QC tries to use the window title (as defined by the original app) as the basis for the temporary document's title, so when I use QC+NV+WR my temp file titles look like "Notation Velocity - Notation 001.txt".

On Tuesday, September 25, 2012 at 3:18 AM, Devin Beecher wrote:

Hi Grey. Thanks for the suggestions! 

I downloaded the website's version of WR and things worked for a while, until just now, when QC broke again. However, I have a new idea of what might have caused it to break.

Normally, I have WR open in the background with no windows open. Invoking QC opens up a new window in WR with an app-specific title, and everything works fine. This time, though, I already had one window open in WR. It was a blank untitled document. When I invoked QC (from Notational Velocity), WR came to the front but did not open a new document. Instead, the old untitled one was made active, and it remained untitled. Then, when I went to save and close that window, I got the Save dialogue box. When I canceled and then closed the document without saving, QC froze up. So maybe it has something to do with a window (or specifically an untitled one) being already open?

Note that I had not yet added "txt" to the list of temporary file extensions. 

I scanned Console for clues, and these are the only lines I could find. I think they are from the time QC broke, but I'm not positive.

Sep 24 23:49:54 Devins-MacBook-Pro.local WriteRoom[1778]: *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
Sep 24 23:49:54 Devins-MacBook-Pro.local WriteRoom[1778]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.

Does this give you any clues?

Thanks,

Devin

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