the last characters are not taken into account if you're typing too fast

do you still have this behaviour with the latest version on dapper? i can't reproduce it here

Yeah, just tried, and it's still there. The little menu displayed under
the desktop-bar (with the different actions which can be triggered)
takes some time to catch up with what i type in the input field. When I
press enter, it seems like it's what's displayed in the menu that's
taken into account, not what's in the input field.

On Wed, 2006-03-29 at 10:10 +0000, Sebastian Dröge wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/34024
>
> Task: ubuntu deskbar-applet
> Status: Unconfirmed => Needs Info
>
> Comment:
> do you still have this behaviour with the latest version on dapper? i
> can't reproduce it here

I just installed Flight 6. I can confirm this bug.

confirmed on flight 6

i still have the issue with dapper up to date. It seems pretty major to me. Is anyone working on a fix?

I have the latest desk-applet from dapper-updates (2.14.2-0ubuntu1) and I still encounter this bug.

With Deskbar applet 2.16.0 (edgy beta) I don't have this behaviour any more. It seems that pressing return does not work until the list is updated to include all typed characters.

Unfortunately, this means that if I type "whatever<ENTER>", the default action will not be triggered if I have not waited for the list to appear before pressing <ENTER>. This means for me that I have to do it this way: "whatever<wait-until-list-appears><ENTER>"

On Dapper, I have it too, on Edgy, I don't, so I will create a dapper task and close the normal one.

Hi Martin,

I played around a bit and found out that it still happens in Edgy.

To reproduce, execute for example gaim and gvim or gconf-editor so that they all appear from history when you type the letter g.
In order to make this bug more obvious, start gconf-editor and edit /apps/deskbar/typingdelay to something big, e.g. 2000 ms.

Now go to the taskbar and type "g". Wait the 2 seconds for the list to appear. gaim will be listed above gvim because of the alphabetical sorting. Now finish typing "gvim" and press enter immediately (without waiting the 2 seconds). Gaim will be executed although you typed "gvim<enter>"

As a workaround I set the typingdelay in gconf-editor to 0 but that's a bit of a dirty hidden trick ;)

This bug is already known upstream. I fear that it is actually far deeper than it appears. Furthermore it also has some side effects that might be unwanted. See http://bugzilla.gnome.org/show_bug.cgi?id=345806.

Specifically on the "side effects". Consider yourself typing in some letters (fast) and you see the match you where looking for pop to the top. You hit enter and expect to activate the match you see. Now because deskbar was actually a split second behind you, you activate the match for your complete (unshown) string, which might be something completely different...

that's a minor bug, will not change to dapper