KDE-Forum.org

like summarised in
bug130623
and
bug50457



i am searching for a tweak to optimizer the widget-spawn-time in kde-menues:

<<<<>>>>
------- Additional Comment #2 From kde@terabytemusic.cjb.net 2006-06-03 10:05 -------
I certainly do not agree with this being 'useless'.

Example: I want to save a file in Kate.

I click File and then move my mouse pointer to Save
But, before I reach Save, the mouse will hover on the Recently opened submenu.
This submenu will open *immediately*. Since there are some long filenames/paths, this menu will cover the rest of the File menu, including the Save option.

If there would be a small configurable delay, then my mouse pointer would reach the Save menu item before the Recently opened submenu would open (and cover the Save menu item).

Conclusion: this is not a "useless configurability", but a usability option that some or many users may need. Setting a small default delay may also be an option.


------- Additional Comment #3 From Christoph 2006-07-12 10:50 -------
i think this is really similiar to my bug 130623 ... is an interface-issue and not useless .. in fact the default "widget-spawn-time" is useless for handycapped people how are not champions with the pointer device .. and anyway i am not handycapped :-IMO) , and it spawns much too fast .. but a setting would affect both, menu and filebrowsing .. i have no problems whith the speed when i navigate in menus, but for the filesystem-browsing via a "quickview"-button its pain in the *$$ to navigate deep folder-structures

regards
<<</>>>

Quoted

Originally posted by trueshanti
i am searching for a tweak to optimizer the widget-spawn-time in kde-menues

maybe its in some configuration file

i think this option is immanent for handycapped users that are no champions on the pointer device .. just try it yourself .. it may be a minor issue , depend who wants it installed

regs.

-c-

Quoted

Originally posted by Aceler
I opened this question 3 years ago in russian KDE forum. This point still have no solution. There is no option in config files. There is no developers who wants to implement this.

it should be implemented in the accessibility-section of the Kontrolcenter ... i think this is a good place for this