just a warning for those who may not have seen my bug report https://quality.livecode.com/show_bug.cgi?id=24196, which turned out to be a duplicate bug report from 2017 and still not fixed: https://quality.livecode.com/show_bug.cgi?id=20279.
Basically any standalone created automatically enables navigation of cards with arrow keys (the navigationArrows is set to true by default). The opposite is true of the IDE, where the navigationArrows is set to false by default and this appears to be a system setting in the IDE preferences, not the stack, so it's not something we're normally conscious of when designing an app.
This means that the behaviour of a stack in IDE and standalone by design is different and not in a good way: Any programming to control navigation of cards in a standalone, not the IDE is automatically thwarted by the user simply pressing the right/left arrow keys if nothing is selected/no field is active, whereby the user can simply go next card wit right arrow etc, and this would not be evident at all when testing in the IDE.
For now the workaround is to
Code: Select all
set the navigationArrows to false
I consider this is a very serious issue especially where a password scheme to control access to cards (this has led to critical security failures in several of my apps, only recently brought to light by beta testers), but would affect any app that controls flow between cards in any way.
Please chime in on the bug reports as the current state of play means that the same stack exhibits different behaviours in IDE and Standalones.
Personally I don't even see the point of such a setting - if arrow navigation is desired I'd simply trap the rawKeyDown message.
Regards
Stam