Although the new Bezel HUD plugin was listed as installed and updated,
I went ahead and re-installed. This got QS back to operating status,
but it still doesn't drill down through folders when I begin typing. I
can access any directory, but when I <space> into the folder I cannot
continue typing to access items within the parent - I have to use the
mouse or arrow keys to scroll down.
Also, I was using a 3rd party HUD (can't remember the name of it),
which now appears to be gone in QS 60 after installing the updated
Bezel HUD.
Aesthetics aside, I really miss being able to type-to-drill. To me,
this was/is the killer feature and time saver of QS.

Thanks for any and all help!!!

On Jun 18, 3:32 pm, Patrick Robertson <[email protected]>
wrote:
> If you're using the Bezel HUD plugin, have you tried downloading the latest
> fromhttp://qsapp.com/plugins
>
> Hopefully that'll help. If not, let us know :)
>
> On 19 June 2011 02:05, neuroman53 <[email protected]> wrote:
>
>
>
>
>
>
>
> > This appears to be a bug within B60. I had the package for B59 saved,
> > and re-installed it after removing B60. The problem no longer occurs,
> > and QS appears to be functioning without a problem.
>
> > On Jun 18, 11:21 am, neuroman53 <[email protected]> wrote:
> > > Went to sleep, QS B60 was working as well as I've been able to get it
> > > to. I haven't done any tinkering with it since the initial setup a
> > > couple of months ago, so I cannot attribute this to anything I did.
> > > This morning, after startup on my computer, QS only brings up the
> > > first hit in the main window, with the details window automatically
> > > and consistently opening up underneath it. The details window has no
> > > other results, however, and when I hit the spacebar (which would
> > > normally drill down in a directory) QS automatically moves down to the
> > > top level/file within the directory. This is confusing, to say the
> > > least. I have repaired disk permissions (for what it's worth),
> > > restarted my machine, and have re-run QS setup. I have stopped short
> > > of resetting defaults and uninstalling/reinstalling, as I'd like to
> > > see if anyone else has had this problem and remedied it.
>
> > > Any thoughts?
>
> > > Thank you

Reply via email to