-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QS switches to starting space when fired from another space #64
Comments
Works for me as expected. Quicksilver shows its icon in the dock, is not specially assigned in System Preferences and appears on the current space as expected. I'm using the Window interface, but I tested with Bezel, Cube and Primer and they also work as expected. Questions:
|
Sorry for the delay. I ran with QS in the dock since the bug appeared. Today I tried to reproduce the bug and QS just ran as it was expected. So QS is not in the dock. The QS quick launch window appears in the space where it is triggered. My interface is Primer with no extra (everything unchecked in the Appearance panel). I close the case as I can't reproduce the bug. Maybe the Mac OS X update just solved the problem. Thank you for your interest in it. |
Funny story: now I'm seeing this bug since the very same update. I'll check everything out and see if I can fix it for myself. |
In my case, it seems to be a matter of whether the icon is shown in the dock or not. If "Show icon in dock" is enabled, Quicksilver appears in the current space; if not, Quicksilver is constrained to the space it was launched in. My setup is probably nothing unusual:
|
I'm also seeing this bug, in Quicksilver b59, and previously on b58. I'm running 10.6.7, and the bug persists since 10.6.3 (that I can recall). After a lot of testing, I discovered that the bug occurs only with Primer interface. |
OK. Thanks for the extensive testing. I will reopen this and change the title to include Primer so some people can look at it. |
Hi Patrick, I also notices (however, tested only on 10.6.7, b59) that when using Bezel interface the same problem occurs only with the preference window. I.e., if I use bezel, and I started QS in the first Space, then if I move to Space#2, and type cmd-space,cmd-comma, I'm switched back to Space#1. Is there some debugging I can turn on to see what is happening? |
Yes, I noticed this with Primer as well and just hadn’t gotten around to reporting it. I forget where (mailing list?) but @bencochran recently said something about fixing issues with Spaces in BezelHUD. Maybe he could offer some tips on how to fix this. |
Thanks for the ping, @skurfer. Should be fixed in pull request #199. |
P.S. It might be worth adding |
I can confirm that this change fixes the issue with Primer interface. Thanks @bencochran. |
Fixes issue brought up in issue #64
Thanks for the confirmation @knl. For the prefpane, see pull request #200 |
Hi @bencochran, with pull requests #199 and #200 both issues are fixed. It works like a charm, thanks! |
Cool. That's 1 confirmation for each. I'll have a test then merge :) On 19 April 2011 04:25, knl <
|
Fixed in latest commit |
This is exactly the same bug as provided there: http://code.google.com/p/blacktree-quicksilver/issues/detail?id=225
What steps will reproduce the problem?
What is the expected output?
I would expect to see the QS window appear awaiting input in the space I am presently in.
What do you see instead?
Spaces switches to whatever space it was in when QS was launched, then shows the input
window in that space.
What version of the product (including Quicksilver version, AND the module version related to
the buggy functionality if appropriate) are you using? On what operating system?
I'm on QS B57 (3840), running Snow Leopard 10.6.2.
Workaround:
with "Every space" while
Quicksilver was running with a visible dock icon
All of this is copy/pasted from issue 225 on the previous issues reporting system.
The text was updated successfully, but these errors were encountered: