Hi, I’m running v2.0-alpha.9503 under OS X 10.9, and habitually view it full screen (ctrl-cmd-f). However I call up the Find/Replace dialog (e.g cmd-f), the editing window turns invisible. This makes the Next button (among others) highlight matches in an invisible document (try it and you’ll see what I mean). No such problem if I exit full screen (ctrl-cmd-f again) before I call up the Find/Replace Dialog. I thought you’d want to be aware of this behaviour.
Regards Robert Milton
I'm using v2.0-alpha.9505 on OS X 10.9.1 and I do not see this behavior. Works fine for me.
On Wed, Feb 5, 2014 at 4:51 PM, Robert Milton <robert.gomez.milton@gmail.com
wrote:
Hi, I’m running v2.0-alpha.9503 under OS X 10.9, and habitually view it full screen (ctrl-cmd-f). However I call up the Find/Replace dialog (e.g cmd-f), the editing window turns invisible. This makes the Next button (among others) highlight matches in an invisible document (try it and you’ll see what I mean). No such problem if I exit full screen (ctrl-cmd-f again) before I call up the Find/Replace Dialog. I thought you’d want to be aware of this behaviour.
Regards Robert Milton
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
Sorry, Curt is right…I missed out a detail I didn’t realise was relevant. Before opening TextMate, assign it to This Desktop (ctrl-click TextMate on the dock, Options->This Desktop). Following my original email then consistently produces the odd behaviour for me.
Assigning TextMate to None instead of This Desktop consistently eradicates the odd behaviour for me, which I suspect explains Curt’s observation.
Out of curiosity I tried exactly the same things with Pages…which always behaves as you would expect (no invisible documents).
On 5 Feb 2014, at 22:57, Curt Sellmer sellmerfud@gmail.com wrote:
I'm using v2.0-alpha.9505 on OS X 10.9.1 and I do not see this behavior. Works fine for me.
On Wed, Feb 5, 2014 at 4:51 PM, Robert Milton robert.gomez.milton@gmail.com wrote: Hi, I’m running v2.0-alpha.9503 under OS X 10.9, and habitually view it full screen (ctrl-cmd-f). However I call up the Find/Replace dialog (e.g cmd-f), the editing window turns invisible. This makes the Next button (among others) highlight matches in an invisible document (try it and you’ll see what I mean). No such problem if I exit full screen (ctrl-cmd-f again) before I call up the Find/Replace Dialog. I thought you’d want to be aware of this behaviour.
Regards Robert Milton
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 6 Feb 2014, at 18:30, Robert Milton wrote:
[…] Before opening TextMate, assign it to This Desktop (ctrl-click TextMate on the dock, Options->This Desktop).
I see no such option here. Do I need to enable something to get this? Or is this perhaps a third party utility?
Mac OS X 10.9.1
On Feb 8, 2014, at 2:30 AM, Allan Odgaard mailinglist@textmate.org wrote:
On 6 Feb 2014, at 18:30, Robert Milton wrote:
[…] Before opening TextMate, assign it to This Desktop (ctrl-click TextMate on the dock, Options->This Desktop).
I see no such option here. Do I need to enable something to get this? Or is this perhaps a third party utility?
I know teacher call on me call on me teacher call on me I know the answer oooooh ooooooh oooooh I had my hand up first!
Under Options in an app's Dock menu you will "normally" see things like this:
Keep in Dock Open at Login Show in Finder
Now launch Mission Control (I do apologize for the stupid way Apple names its applications). Swing the mouse to the top right of the screen until you see a big "+" appear. Click it. Click on the backdrop to dismiss Mission Control.
Now you have multiple "spaces", now known as Desktops.
Now Options also has an Assign To Desktop category:
All Desktops Desktop 1 Desktop 2 [etc.] None
In other words, you won't see the phenomena associated with multiple Desktops unless you _have_ multiple Desktops. m.
-- matt neuburg, phd = matt@tidbits.com, http://www.apeth.net/matt/ pantes anthropoi tou eidenai oregontai phusei Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
On 6 Feb 2014, at 18:30, Robert Milton wrote:
Sorry, Curt is right…I missed out a detail I didn’t realise was relevant. Before opening TextMate, assign it to This Desktop (ctrl-click TextMate on the dock, Options->This Desktop). Following my original email then consistently produces the odd behaviour for me.
Based on Matt’s instructions, I have now been able to try this. However, I see a different behavior.
When I create an additional desktop, lock TM to one of them, go full screen, and press ⌘F (with no Find window showing in any space) I am brought back to the desktop that I have locked TM to, and the Find window is shown on that desktop.
If the Find window is already showing, ⌘F will move it to my active desktop.
It seems like an edge-case that Apple mishandles. I.e. when a window is full screen, auxiliary windows should ignore that the app has been locked to a desktop (and should instead show on the desktop with the full screen primary window).
Out of curiosity I tried exactly the same things with Pages…which always behaves as you would expect (no invisible documents).
You can create regular windows, panels, floating (utility) windows, etc., and in addition, you can set some explicit “window collection behavior” like NSWindowCollectionBehaviorMoveToActiveSpace — all of this is taken into consideration when the OS decides how to “manage” the windows, so Pages might use a window where TM uses a panel, or it might set some semi-abstract collection behavior flag.
To my knowledge, nowhere does Apple document what the expected behavior should be for the various window types and collection behavior flags, wrt. multiple desktops behavior.
I suspect we see exactly the same behaviour…which I didn’t describe very precisely. The weird looking bit is that the OS doesn’t take you back the Full Screen document, which can give the impression it’s turned invisible. In particular if you use the “Next” button to step from match to match the effect looks a bit like a transient spark on the desktop, as the match is briefly highlighted without actually returning to the Full Screen document…Hopefully you can see what I mean on the attached screenshot.
I now realise this is an edge case (polite term for user misbehaviour) OS X doesn’t handle very well. Put bluntly, assigning an App to a Desktop and using it Full Screen isn’t how OS X wants to work. I’d never have realised this without Curt’s original response. I hope you don’t feel this has been a complete waste of time.
Maybe Apple could handle this user error a bit better. My guess would be that full screen apps + multiple desktops increasingly appeal to the average user until the tide turns back towards bigger (17inch+) displays.
On 9 Feb 2014, at 15:47, Allan Odgaard mailinglist@textmate.org wrote:
On 6 Feb 2014, at 18:30, Robert Milton wrote:
Sorry, Curt is right…I missed out a detail I didn’t realise was relevant. Before opening TextMate, assign it to This Desktop (ctrl-click TextMate on the dock, Options->This Desktop). Following my original email then consistently produces the odd behaviour for me.
Based on Matt’s instructions, I have now been able to try this. However, I see a different behavior.
When I create an additional desktop, lock TM to one of them, go full screen, and press ⌘F (with no Find window showing in any space) I am brought back to the desktop that I have locked TM to, and the Find window is shown on that desktop.
If the Find window is already showing, ⌘F will move it to my active desktop.
It seems like an edge-case that Apple mishandles. I.e. when a window is full screen, auxiliary windows should ignore that the app has been locked to a desktop (and should instead show on the desktop with the full screen primary window).
Out of curiosity I tried exactly the same things with Pages…which always behaves as you would expect (no invisible documents).
You can create regular windows, panels, floating (utility) windows, etc., and in addition, you can set some explicit “window collection behavior” like NSWindowCollectionBehaviorMoveToActiveSpace — all of this is taken into consideration when the OS decides how to “manage” the windows, so Pages might use a window where TM uses a panel, or it might set some semi-abstract collection behavior flag.
To my knowledge, nowhere does Apple document what the expected behavior should be for the various window types and collection behavior flags, wrt. multiple desktops behavior.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On Feb 10, 2014, at 11:59 AM, Robert Milton robert.gomez.milton@gmail.com wrote:
I now realise this is an edge case (polite term for user misbehaviour) OS X doesn’t handle very well.
Calling this an "edge case" is extremely kind. Basically Mavericks is just a lot of stuff that hasn't been thought through very well, piled on top of each other. m.
-- matt neuburg, phd = matt@tidbits.com, http://www.apeth.net/matt/ pantes anthropoi tou eidenai oregontai phusei Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html TidBITS, Mac news and reviews since 1990, http://www.tidbits.com