perhaps you could use OBJECT SET EVENTS
http://doc.4d.com/4Dv16/4D/16.3/OBJECT-SET-EVENTS.301-3651506.en.html
to disallow the default button's click event during text edit. (its more subtle
than disabling them)
> 2018/01/26 0:35、Jim Crate via 4D_Tech <4d_tech@lists.4d.com> のメール：T
> I’m not
> Le 25 janv. 2018 à 16:35, Jim Crate via 4D_Tech <4d_tech@lists.4d.com> a
> écrit :
>
> I’m not trying to filter user input. I’m trying to trap certain
> navigation-related keystrokes. I am trying to implement a relatively simple
> generic auto-complete that allows me to customize the query
I’m not trying to filter user input. I’m trying to trap certain
navigation-related keystrokes. I am trying to implement a relatively simple
generic auto-complete that allows me to customize the query used to generate
the autocomplete list. I’m displaying a listbox under the field the user types
the "On Losing Focus" event fires as a "result" of another object taking its
focus way.
is the default button focusable?
I don't think you can write generic code without knowing the next/previous
object in entry order.
also, keystrokes are not the only way to edit text, it can be drag and
I would like to intercept the tab/return/enter keys using the On Before
Keystroke form event. However, with a default button on the form, I don’t even
get an On Losing Focus event. With the default button not specified, the return
key functions the same as a tab, so I can detect losing focus at
5 matches
Mail list logo
