arrow keys

[Scott Richardson]

This may be a silly question, but is there a practical way to disable the use of the arrow keys on the keyboard to navigate from card to card for a stand-alone application? I need to restrict the end-user from being able to move from card to card in a linear fashion.
Thanks,
Scott

[FourthWorld]

See the Rev Dictionary entry for the navigationArrows global property.

[Scott Richardson]

No wonder I couldn't find what I was looking for ... I was calling it the wrong thing. Thanks for putting me on the right track.
Scott

[FourthWorld]

Just out of curiosity, what were you searching for?

Finding out terms new users search for can help make for a better index.

Thanks -

[Scott Richardson]

Forgetful me — I was thinking in terms of the keyboard and not the application and searching for things related to "keys" and not "arrows" or "navigation."

By the way, for the global property to be false when I create a standalone application, do I need to have a custom property set or anything? When I changed the global property to false it worked fine, but when I saved the stack as a standalone app, the arrow keys still functioned. Something that seems to be related is the backdrop. When I set it "on" or "off," it works great until I save the stack as a standalone, then the backdrop is off. I have read and re-read the User Guide section on global properties, but I am still confused about implementing them in a standalone.

Thanks again,
Scott

[FourthWorld]

The Dictionary says that the default value for the navigationArrows is true, so to disable it you'll want to turn it off in whatever handler you use to initialize your app (I tend to use preOpenStack in the card of the mainstack so I get my initialization both at runtime and in the IDE, but others prefer to do their initialization in a startup handler).

[Scott Richardson]

I wanted to leave a word of thanks for you. I appreciate the help in getting me pointed in the right direction (pun intended) with the arrow keys. Also, the preOpenStack worked best for my situation, too. Thanks again.
Scott