you could parse the xml returned from the export structure command.
**
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:
> On 3 Dec 2019, at 21:47, Peter Bozek wrote:
> But doing it again, I would go for something simpler.
…and that “something simpler” turns out to be Jeremy Roussak’s tip of removing
the “Focusable” property from the default button on the form.
This is the key to everything, including:
1. The
Sorry to enter the thread late, but tried to implement similar
functionality several years ago. Ended up with variable set in On getting /
on loosing focus. Button that handled Enter checked value of the variable
and either processed script or saved record.
Final implementation was more complex,
I use the properties parameter, returned from AP Get field infos command in
4D Pack. This command is now deprecated in v16 and replaced with similar
(but not equivalent) commands in v17 itself. With the number 1 and number 2
bits returned in this parameter, I can tell the deletion control settings
Typo in the previous message -
not 120 ticks 20 or 30 :)
On Tue, 3 Dec 2019 15:21:39 +, Peter Jakobsson wrote:
> Hi Chip
>
> Thanks for the reply. I’ve seen that approach on some web based systems.
>
> Could be good, could be bad. I see some users loving it and others
> hating it. The
Hi Chip
Thanks for the reply. I’ve seen that approach on some web based systems.
Could be good, could be bad. I see some users loving it and others hating it.
The machine trying to “second guess” that the user has typed enough into the
filter field sometimes makes it feel flaky because it’s
have you considered using a timer to auto search for the user?
i.e. user types: "App"
and after a brief delay the searches auto executed using the user
entered information? I use 120 ticks.
then they do not have to hit return at all
On Tue, 3 Dec 2019 00:26:24 +, Peter Jakobsson via
7 matches
Mail list logo
