Incremental search

[usamin02]

I want the function of incremental search.
Portabase (version 2.1) has that function. By typing in several characters, the cursor moves to the record corresponding to these characters.

[jmbowman]

Where do you want it implemented? That's a built-in feature of the Qt item view widgets, so like you say it should already be working in all of the list-type widgets in PortaBase, as long as they have keyboard focus.

[usamin02]

On the data_viewer screen of portabase2.1(Sharp Zaurus edition , Windows edition and so on), I can incrementally search records by hitting sevral characters corresponding the leftmost table. I can incrementally search records by entering sevral characters at the beginning condition on the filter screen of poratabase 2.2, but I must erase the characters for next search. I would like to incrementally search on the data_viewer screen by displaying software keyboard. 2017-12-04 13:52 GMT+09:00 Jeremy Bowman <notifications@github.com>:

…

Where do you want it implemented? That's a built-in feature of the Qt item view widgets, so like you say it should already be working in all of the list-type widgets in PortaBase, as long as they have keyboard focus. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#31 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AglFvIT0XSWnGMW-7_f3zwlt2PbcT0xzks5s83qogaJpZM4QyViw> .

[jmbowman]

Ah, on the Android version? I'll see if I can add a button/menu item to display the keyboard while the data viewer is showing; that should enable the incremental search, I'll try to confirm that.

[jmbowman]

I have a first pass at this in testing. The way it currently works:

• An item on the action bar (Keyboard icon when it fits on the bar, "Incremental Search" text when pushed into the overflow menu) launches the software keyboard.
• You can enter the search text in the keyboard; there is no immediate reaction from the underlying display.
• When the keyboard is closed, the next item starting with the entered text is scrolled to and selected.

@usamin02 Does that sound good enough for a first release of the feature? It might be possible to get the data grid to respond immediately to input, but that probably also runs the risk of making it difficult to enter multi-letter search terms quickly enough to not register as a new one-letter search instead. (Also, I'd have to investigate how to do that, and currently have no idea how long it would take to figure out.)