diff options
author | Mathias Gumz <akira@fluxbox.org> | 2015-01-28 15:02:59 (GMT) |
---|---|---|
committer | Mathias Gumz <akira@fluxbox.org> | 2015-01-28 15:02:59 (GMT) |
commit | 03ce82a4737b834767c03341db9362ada24c775a (patch) | |
tree | 2444031bbd47d97b1e0af64aa2f1d2a037a08a2e /data/styles/zimek_bisque/theme.cfg | |
parent | fc245408d6975d0813cd4440e7089d987b54d42e (diff) | |
download | fluxbox-03ce82a4737b834767c03341db9362ada24c775a.zip fluxbox-03ce82a4737b834767c03341db9362ada24c775a.tar.bz2 |
Feature: typeahead in menu matches text anywhere
This commit implements a tweak to the typeahead feature already existent in
fluxbox: If the user opens up a menu and starts typing, fluxbox tries to
detect matching menu items and makes them available for quick selection.
The typed pattern is now search also in the middle of the text.
I opted to strip down the code quite a bit and remove complexity by throwing
out FbTk::TypeAhead and FbTk::SearchResult because I do not see the need for a
general solution when the only use case for such a feature is in fluxbox'
menus. FbTk::ITypeAheadable shrunk down to 2 functions; the whole file might
be combined with the code that implements FbTk::Menu::TypeSearch.
FbTk::Menu::setIndex() and related code is also gone: the position of each
menu item is defined by it's position in the items container. This reduces the
mount of book keeping fluxbox has to do. Fewer moving parts is a good thing.
It's possible that users start to complaint because they expect their
typed pattern to match only at the beginning of the text OR that some
demand other tweaks. We will see.
This commit also fixes a regression introduced by 8387742c. The bug made
the menu vanish.
Diffstat (limited to 'data/styles/zimek_bisque/theme.cfg')
0 files changed, 0 insertions, 0 deletions