Unity DASH is very SLOW At Binding To KEYBOARD INPUT - Misses typed text

[John M.K.]

When pressing the Super-Key (or Windows-Key if you may), Unity takes unacceptably and unpredictabely long (quit random) to bind to the keyboard input.

So if you press the SuperKey and immediately start typing, part of what you write becomes lost.

Mouse input etc. can be postponed until the Dash renders, but the specifications for keyboard input response time should be more stringent, IMO.

I think that this should be part of the design specs for the Dash in general, in as much as Dash provides the new access point for the applications and files. Being part of the design specs will assure that this spec is going to be percistently met at future releases...

[John Lea (johnlea)]

This is technical bug, not a design bug, so assigning to project Unity. The text input is specified to be available instantaneously after the Dash is opened.

[John M.K. (jconni)]

Ok, correct. In that case my point is that technically there is a difference between the Dash being opened (renders on screen), and the Dash being prompted to open (user clicks icon or presses super key).

 I believe that the specs should demand for immediate keyboard input binding at prompt to open, not at actual opening (rendering). I don't know if there is a technical limitation for that, but an independent thread always sleeping in the background ready to simply bind to keyboard input at request would be even better, for superior response time.

Since this release is advertised, amongst others, to focus more into Power-users, I beleive this is one feature not to overlook.

[Omer Akram (om26er)]

Thanks for the bug report. This particular bug has already been reported and is a duplicate of bug 891210, so is being marked as such. Any further discussion regarding the bug should occur in the other report. Feel free to report any other bugs you may find.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.