Post Reply 
newRPL: [UPDATED April 27-2017] Firmware for testing available for download
03-02-2017, 10:38 PM
Post: #592
RE: newRPL: [UPDATED February 21-2017] Firmware for testing available for download
(03-02-2017 05:27 PM)rprosperi Wrote:  I disagree, STOKEYS is much more flexible (and easier to use in many cases) than ASN, particularly when setting more than 1 assignment. Also, when changing some assignments, it's easiest to RCLKEYS, edit the list and then STOKEYS to save changes.
This I understand and agree, RCLKEYS/STOKEYS should have a translation to the internal format, but should be presented in user-editable form.

(03-02-2017 05:27 PM)rprosperi Wrote:  In fact, the manual specifically recommends STOKEYS when making multiple assignments. Finally, STOKEYS also is the way one restores the default assignments via the initial "S" in the list.

I like the extra context modes, it will allow a bewildering set of assignments (a good thing, I think). So this is a benefit too.

The reason is recommended is because they want to assign single commands which can only be typed inside a list. This is not needed in newRPL, you can put the command inside a program and it will work well.

The S feature doesn't exist in newRPL. Why? Because its purpose is to enable or disable the default behavior. This is exactly what changing the context does. Some contexts exist in the system and have default key assignments (like the stack, interactive stack, editor). Now other (user) contexts are a blank canvas. The context switching will be tied to the Forms engine, you can define as many contexts as you want/need for different activities in your application (like data input, viewing a plot, etc). You only make the custom assignments once at the beginning of your program, then simply switch contexts and keys will activate/deactivate. Context 0 is a wildcard for a key that works on all contexts.
Default behaviors are always there for the standard contexts and cannot be disabled globally (but can be overridden individually with a key definition). When your application ends, context goes back to the stack and all keys go back to normal, whether you cleanup your definitions or not.

In case you override an important key (like ENTER) in the stack and can't use the calc anymore, there's a flag to disable custom keys in the menu. I'll eventually add a shortcut with On+SOMETHING that disables custom keys.

(03-02-2017 05:27 PM)rprosperi Wrote:  Will CST be affected? I.e. can CST menu assignments be extended with the additional planes and contexts?

Menus are a completely different definition from keys, and for now are completely independent from contexts, although each Form will have their own keyboard context and menu, hence they will indirectly be linked. But to answer your question, menus won't be affected by the change.
Menu definitions support all planes except no key_UP, key_DN, or repeat events (just press and long press with various shifts).
Oh, and there's no 'CST' anymore. You can assign any variable identifier to the menu (as in 'MYVAR' TMENU), in other words, there's as many 'CST' menus as you want, named whatever you want.
There will be (eventually) a key named CST (still don't know where to put it in the keyboard), that will run a menu named 'CST' for old times sake.
Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
RE: newRPL: [UPDATED February 21-2017] Firmware for testing available for download - Claudio L. - 03-02-2017 10:38 PM

User(s) browsing this thread: 2 Guest(s)