Community
Participate
Working Groups
I tend to use much the Open Type dialog (by using the keyboard shortcut, Ctrl-Shift-T on my platform). One thing that annoys me a little bit is that whenever I do not notice that the dialog isn't opened yet and I start typing the class name I'm searching for, this ends up into a mess (typical result is that lastest typed letters get into the input field, which is not what I want). Admittedly, once the cache is warmed up, the UI is fast enough to catch everything I type flawlessly. But whenever the cache needs a refresh, I have to clear the input field and type the name again starting from scratch. I would suggest that keystrokes happening during the cache refresh be queued somewhere and fed to the input field as soon as it gets active. Not sure this would be the best way to do it though and I trust you would have better ideas than me on the right design for the function. The objective stated in user terms would be that when I suddenly think I need type Dummy I can hit Ctrl-Shift-T and type in dumm... without taking care of waiting for the dialog to appear.
Maxime, I already looked into queing the keystrokes but due to SWT and how progress reporting is working this is not possible (the window systems handles the keystrokes and correclty reports them to the "disabled" dialog showing progress). What I have in the pipeline is code that the consistency of the history is restored in the background. This will go into M3. Sorry, nothing else I can do here.
Dirk, thx for the answer. If you cannot close the gap, anything you'll do to narrow it will be welcome, and if I get you well, your upcoming changes will improve the situation. I'll watch this one in M3. (Note: depending on how fast it becomes, maybe having the progress dialog complain - beeps - when the user types in before the Open Type dialog shows up would help a bit? I hope it will be fast enough in itself. I do not type in so fast myself!)
