Full screen apps are above the QS Window [Fix coming soon]

[pjrobertson]

When using full screen apps, QS's command window does not show.

Presumably there's another layer that the interfaces should be changed to use now that there's a 'full screen app' layer.

[ghost]

i can't reproduce this with either the Menu, Bezel, Mini-Bezel or Menu interfaces

[pjrobertson]

Hmm... strange. I can reproduce it with Bezel and BezelHUD interfaces. I
think I remember a twitter user saying the same thing.

I haven't installed the update via software update yet, so I'll see if that
makes a difference.

I have a clean install of Lion, so I guess there are probably a few prefs
that I've left out. I'll look into it and try and figure out what's wrong

On 23 June 2011 10:42, neurolepsy <
reply@reply.github.com>wrote:

i can't reproduce this with either the Menu, Bezel, Mini-Bezel or Menu
interfaces

Reply to this email directly or view it on GitHub:
#391 (comment)

[ghost]

the full screen app thing dynamically creates a Space for each full screen app - could it be a Spaces related bug?

[pjrobertson]

OK it's now suddenly started working. :S
When changing interfaces, the QS window does seem to flicker a bit for me
and then disappear so there may still be a spaces-related bug

On 23 June 2011 11:01, neurolepsy <
reply@reply.github.com>wrote:

the full screen app thing dynamically creates Spaces for each full screen
app - could it be a Spaces related bug?

Reply to this email directly or view it on GitHub:
#391 (comment)

[ulrichvoss]

I can confirm this bug for the "Primer interface" while the "Bezel interface" works fine.

[pjrobertson]

I think I may have found the bug.

To any other interface developers out there (@bencochran)

QSInterface windows should have

    [[self window] setLevel:NSPopUpMenuWindowLevel];
    [[self window] setCollectionBehaviour:NSWindowCollectionBehaviourTransient]; // the default when the window's level **isn't** NSNormalWindowLevel

Note that these changes are 10.6+ only. We will be dropping 10.5 support as soon as we release a build with a plugins update system

[ghost]

i can't quite remember how weak linking works, but i think if you wrap that second line in if (&NSWindowCollectionBehaviourTransient)and it'll work under 10.5.

[thisgeek]

Can't reproduce in v60 1(3850) using Primer. It's weird that others are seeing the issue. I wonder if it's that I did not do a clean install of Lion.

[ulrichvoss]

I haven't done a clean install of Lion either and see this problem. Strange ...

[jxpx777]

I'm still seeing this issue with the Nostromo interface. Does not appear to happen with Bezel.

[skurfer]

It’s a per-interface change, so it won’t be fixed across the board. I could never reproduce it with Nostromo, and I didn’t want to hard-code behavior to fix something that didn’t appear to be broken. Although the only time I run anything full screen is for 3 seconds to test issues like this, so maybe I’d see it if I ran that way longer. Actually, I just tried making the Dock icon show up and now I see what you mean. It’ll get fixed in the next release.

[pjrobertson]

@skufer - you can re-build and push straight to the repo. Why wait until the next release... ;)

Unless you're thinking of making a pull request. Changes are the same as what I made so I'm happy

[skurfer]

I meant the next release of the plug-in, not Quicksilver. I’ve already made the change and committed it (if anyone comfortable with Xcode can’t wait), but there’s other stuff I’d like to do before releasing it.

[skurfer]

Update released, squeaky wheels! ;)

[cablehead]

Not sure if I'm the only one. I still get this with BezelHUD. The builtin Bezel works fine.

[pjrobertson]

Not sure if I'm the only one. I still get this with BezelHUD.

I updated the code, but am not sure if I re-built and released a new
plugin. Thanks for letting us know, I will check it out.

On 29 November 2011 06:10, Andy Gayton <
reply@reply.github.com

wrote:

Not sure if I'm the only one. I still get this with BezelHUD.

---

Reply to this email directly or view it on GitHub:
#391 (comment)

[jxpx777]

Update released, squeaky wheels! ;)

Still not working in Nostromo here. Just double checked that I had the latest release before posting here.

[pjrobertson]

@skurfer should have fixed the problem with the Nostromo interface. Sorry
Andy, I have yet to check if the updated BezelHUD plugin has been released.

Perhaps - Rob you could just check the version number in bencochran's repo
(Info.plist) reflects the released version number? Unfortunately I am
swamped at the moment.

On 15 December 2011 14:18, Jamie Phelps <
reply@reply.github.com

wrote:

Update released, squeaky wheels! ;)

Still not working in Nostromo here. Just double checked that I had the
latest release before posting here.

---

Reply to this email directly or view it on GitHub:
#391 (comment)

[skurfer]

Rob you could just check the version number in bencochran's repo (Info.plist) reflects the released version number?

Looks like the published version is a version back from the most recent commits. I’ll try to build and release it tomorrow if I get time.

[pjrobertson]

Great, thanks Rob :)

On 16 December 2011 03:26, Rob McBroom <
reply@reply.github.com

wrote:

Rob you could just check the version number in bencochran's repo
(Info.plist) reflects the released version number?

Looks like the published version is a version back from the most recent
commits. Ill try to build and release it tomorrow if I get time.

---

Reply to this email directly or view it on GitHub:
#391 (comment)

[skurfer]

New BezelHUD uploaded.

[cablehead]

Thanks Rob, that's fixed things for me. Appreciate it!

[pjrobertson]

Thanks as well Rob :)

On 16 December 2011 16:21, Andy Gayton <
reply@reply.github.com

wrote:

Thanks Rob, that's fixed things for me. Appreciate it!

---

Reply to this email directly or view it on GitHub:
#391 (comment)