ben at pca.com
Fri Jun 17 22:29:45 UTC 2022
The ‘overhead’ I was referring to was having to deal with the keyEvents, as well as having 3 screen fields that have to be in the proper order for this to work. A field for the names, another for the combo list, and a third to handle what happens when the user does a shift-tab from a subsequent field.
I last used this technique in 2002, on a window used to enter long part numbers that were mostly on file. I found it to be a huge time saver. After a few hours work copying my old code, I have it working on a new application.
I was hoping that O$ had a less intensive way to do this entry.
> On Jun 17, 2022, at 6:37 AM, John Boehme <john at integralservices.biz> wrote:
> I have a method in my base window class that is called on the key events of a field. With some parameters it performs a lookup, and list navigation.
> One base class method for the lookup, and one line call to the procedure from the event handler with some parameters is all that is needed.
> What is the "overhead" in StudioTips for this operation?
> John Boehme
> -----Original Message-----
> From: omnisdev-en [mailto:omnisdev-en-bounces at lists.omnis-dev.com] On Behalf Of Ben Weinberg
> Sent: Wednesday, June 15, 2022 2:43 PM
> To: OmnisDev List - English
> Subject: Type ahead
> Hi List:
> Is there a new and less complex method of implementing a type-ahead entry field than the one from Studiotips? I have used that version for years and it works well, just has a lot of ‘overhead’.
> Ben Weinberg
> Manage your list subscriptions at https://lists.omnis-dev.com Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
> Manage your list subscriptions at https://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
More information about the omnisdev-en