I've got an app whose interface exists entirely in a single floating
window and I'm sure a few other people have noticed that Spaces has
issues with tools in that category. The most prominent failure is
that setting an app to appear in all spaces doesn't "just work" but
someone on (I think) this list posted a workaround involving
NSWindow>>setCollectionBehavior:.
Bug #2: I let the user configure my app to allow clicking through to
the desktop, and after a space switch when the window has been told
it can join all spaces, the window loses track of that setting.
Querying ignoresMouseEvents returns YES, but clicks are absorbed by
my window. The workaround seems to be to repeatedly send
setIgnoresMouseEvents:YES to the window.
Bug #3 was reported today. When the window is configured to live on
all spaces and the user switches to a space that contains no app
windows other than Finder, the app that was frontmost on the prior
space retains control of the menu bar. If there are any apps other
than Finder visible in the new space, the menu bar is updated
correctly, even if the active app in that space is Finder. I have no
workaround for this yet, but wondered if anyone else had run into it
and/or had suggestions.
Greg
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
