I noticed the Spaces problem recently with QS B60 using the window interface (version B4)—this was the first time it occurred for me after years of using QS and Spaces together. I tried checking for new plugins via QS's preferences, but was told that everything was up-to- date. Just now I came here to search for the Spaces problem. Henning's post prompted me to check the plugins page, and I found that there is a new version of the window interface plugin (version A4). After I installed that and restarted QS, the Spaces issue no longer occurs (i.e., QS is present on all spaces without changing anything in the Expose & Spaces preference pane).
Thus, two things: 1) check on your interface plugin version, and 2) it will be nice when QS internally/automatically update plugins (that is planned, right?). On Jun 20, 7:33 am, Henning Jungkurth <[email protected]> wrote: > hmm...there have been a lot fixes in regard to spaces recently. Maybe > the things you're talking about are already fixed. > Which version of Quicksilver are you using? Which interface? and Which > version of the interface? > > > > On Mon, Jun 20, 2011 at 3:24 PM, Dan Trimble <[email protected]> wrote: > > I've recently become a fan of using Apple's built-in Spaces features > > to split my running applications across "separate", multiple > > desktops. I do a great deal of research, so I tend to go back and > > forth between web browsers, office apps, email, etc. Breaking it into > > a research desktop, an email desktop, etc. has been a good boost to > > productivity. > > > However, I have one annoyance with using QuickSilver in this kind of > > environment. It's a relatively minor annoyance, but I'm wondering if > > there's any way to fix it, whether a plugin, setting, or even an > > AppleScript. > > > If I'm working on, say, my 2nd desktop in Spaces and double-tap > > command to bring up QuickSilver, it switches over to the 1st Spaces > > desktop to open QuickSilver's command window. It makes sense -- > > QuickSilver loads automatically when the OS starts up, which of > > course, would be in the 1st Space, and so the OS believes it needs to > > open the QS window in the space in which it's running. > > > QS will then process whatever command I tell it and switch back to my > > active Space. It's a modestly annoying interruption in my workflow, > > so I'm curious if there is there any way to have QuickSilver open its > > command window in whatever Space happens to be active when I invoke > > the window? > > > Dan
