HP Forum Archive 20

[ Return to Index | Top of Index ]

[WP 34S] A-D double duty suggestion Message #1 Posted by Dominic Richens on 15 Oct 2011, 8:27 p.m. Right now, XEQ A runs LBL A just like pressing A directly. However we can make XEQ A run LBL 11 instead by removing the NO_SHORT from regA_idx, regB_idx, regC_idx, regD_idx, We would need a small change to process_key() to still allow us to enter LBL A in program mode. if (shorthand && State2.runmode) This gives us another 4 "quick call" labels and if we want to keep those keys as Sigma+, 1/x, y^x and sqrt(x) we can use 11-14 instead of A-D as labels.

Re: [WP 34S] A-D double duty suggestion Message #2 Posted by Alexander Oestert on 16 Oct 2011, 1:46 a.m., in response to message #1 by Dominic Richens I think XEQ A runs LBL 'A', which is different from LBL A, IIRC. Edited: 16 Oct 2011, 1:48 a.m.

Re: [WP 34S] A-D double duty suggestion Message #3 Posted by Walter B on 16 Oct 2011, 2:18 a.m., in response to message #2 by Alexander Oestert Please see "Addressing Labels" - page 24 of the manual :-) Edited: 16 Oct 2011, 3:58 p.m. after one or more responses were posted

Re: [WP 34S] A-D double duty suggestion Message #4 Posted by Marcus von Cube, Germany on 16 Oct 2011, 12:59 p.m., in response to message #3 by Walter B Walter, read the docs (or change them if they are wrong on this)! There is absolutely no connection between labels 'A' and A and there is no shortcut to address label 'A'. To access subroutine 'A' you need to press XEQ ENTER^ A ENTER^. XEQ A and A do the same if A is defined as a label and is not used as a digit (where f+A takes this duty). Back to Dominc's suggestion: It will cause more grief then fun because it's unexpected behavior. If you want a shortcut to label 11 just use XEQ f A.

Re: [WP 34S] A-D double duty suggestion Message #5 Posted by Walter B on 16 Oct 2011, 3:55 p.m., in response to message #4 by Marcus von Cube, Germany :-? Marcus, you go out on a limb there. I'd recommend you read said page yourself thoroughly instead of claiming anything pointless. What you wrote is exactly what the manual says. Edited: 16 Oct 2011, 3:59 p.m.

Re: [WP 34S] A-D double duty suggestion Message #6 Posted by Marcus von Cube, Germany on 17 Oct 2011, 2:12 a.m., in response to message #5 by Walter B Sorry, I misread your comment in that you were seconding Alexander's remark. I remember that there was such a confusion in an earlier version of the manual. Your answers are often just a bit terse: "RTFM on page xyz!" instead of citing or rephrasing a few words. So the reader never knows what the essence of your post is, except he goes to the file system, fires up Acrobat Reader with the manual, goes to page xyz, finds the corresponding text, and then returns to the forum in order to re-read and answer your post. That was just too demanding for me on a Sunday afternoon.

Re: [WP 34S] A-D double duty suggestion Message #7 Posted by Walter B on 17 Oct 2011, 4:03 a.m., in response to message #6 by Marcus von Cube, Germany In fact, I seldom write RTFM unless well deserved ;-) I think, however, that manual is written and maintained to be read. And sometimes I hate repeating what I wrote (hmmmh, maybe more than sometimes).

Re: [WP 34S] A-D double duty suggestion Message #8 Posted by Alexander Oestert on 17 Oct 2011, 4:13 a.m., in response to message #6 by Marcus von Cube, Germany Quote: Sorry, I misread your comment in that you were seconding Alexander's remark. Well, I did also. Even after reading said manual page a couple of times now I still am confused. ;) Edited: 17 Oct 2011, 4:24 a.m.

Re: [WP 34S] A-D double duty suggestion Message #9 Posted by Walter B on 17 Oct 2011, 4:24 a.m., in response to message #8 by Alexander Oestert Quote: Even after reading said manual page a couple of times now I still am confused. Don't hesitate to ask questions. Please quote what's confusing you :-)

Re: [WP 34S] A-D double duty suggestion Message #10 Posted by Alexander Oestert on 17 Oct 2011, 4:32 a.m., in response to message #9 by Walter B Quote: what's confusing you :-) In a word? The manual! ;) Please don't get me wrong, I'm not complaining. I'm just a guy who needs at least a five lines code snippet to accompany every single function in the manual, every necessary keystroke written down. Without that I find myself all searching at the wrong places or the wrong keywords.

Re: [WP 34S] A-D double duty suggestion Message #11 Posted by Dominic Richens on 17 Oct 2011, 6:22 a.m., in response to message #10 by Alexander Oestert Alex, Sounds like you should be contributing to the wiki Users Guide :-) With Walter's pointer, I did peruse page 24 and yes, it does say it right there (in 3rd column and footnote 14). All the information is in the manual, but sometimes it feels like that little bit you are looking for is "in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying 'Beware of the Leopard'".

Re: [WP 34S] A-D double duty suggestion Message #12 Posted by Alexander Oestert on 17 Oct 2011, 6:38 a.m., in response to message #11 by Dominic Richens As soon as I understand a topic, I might eventually try to put that in words, although I am not so sure I can do it any better. Re-reading the manual and Walter's statement on it above, I guess I know now what got me confused: Walter's posting first said 'Correct' before he edited that out. I'm actually happy to see him confused with the manual, too. ;-)

Re: [WP 34S] A-D double duty suggestion Message #13 Posted by Dominic Richens on 16 Oct 2011, 6:00 a.m., in response to message #2 by Alexander Oestert Is this new? In 1664 XEQ A run LBL A just like pressing A directly. XEQ ENTER A ENTER runs LBL 'A (four keys strokes)

Re: [WP 34S] A-D double duty suggestion Message #14 Posted by Paul Dale on 16 Oct 2011, 2:29 a.m., in response to message #1 by Dominic Richens I don't like this much. How do I enter XEQ A in a program before I've defined LBL A? Doing this also loses consistency between run and program modes. The same keystrokes should do the same thing in both. - Pauli

Re: [WP 34S] A-D double duty suggestion Message #15 Posted by Dominic Richens on 16 Oct 2011, 6:18 a.m., in response to message #14 by Paul Dale Quote: How do I enter XEQ A in a program before I've defined LBL A? That does not change. Quote: Doing this also loses consistency between run and program modes. The same keystrokes should do the same thing in both. Agreed, for the first four labels - if they are used. Edited: 16 Oct 2011, 6:19 a.m.

Re: [WP 34S] A-D double duty suggestion Message #16 Posted by Dieter on 16 Oct 2011, 7:32 a.m., in response to message #14 by Paul Dale I like the idea of four additional hotkeys in addition to A...D. Maybe because I am used to the 41C which has no less than 15 of these. So I think something like [prefix] [A] would be nice. For instance, as mentioned, [A] and [XEQ] [A]. Dieter

Re: [WP 34S] A-D double duty suggestion Message #17 Posted by Marcus von Cube, Germany on 16 Oct 2011, 1:03 p.m., in response to message #16 by Dieter A to D have functions on the shift planes which would be unaccessible if we'd allow for a prefixed A to D shortcut. XEQ f A calls XEQ 11.

Re: [WP 34S] A-D double duty suggestion Message #18 Posted by Dieter on 16 Oct 2011, 5:33 p.m., in response to message #17 by Marcus von Cube, Germany Quote: A to D have functions on the shift planes which would be unaccessible if we'd allow for a prefixed A to D shortcut. Actually I had some other kind of prefix keys in mind. But honestly, I simply forgot the following feature: Quote: XEQ f A calls XEQ 11. This will do. At least until the h-shifted functions of A...D go to a DISP menu in favour of four new hotkeys like a...d or A'...D'. ;-) Dieter

Re: [WP 34S] A-D double duty suggestion Message #19 Posted by Dominic Richens on 16 Oct 2011, 8:13 p.m., in response to message #17 by Marcus von Cube, Germany But that's inconsistent with the other shortcut keys, like STO, where XEQ STO call LBL 21. I was trading runtime inconsistency for programming inconsistency, favouring the one that means fewer keystrokes at runtime. It also frees up XEQ f to call LBL 24.

Re: [WP 34S] A-D double duty suggestion Message #20 Posted by Marcus von Cube, Germany on 17 Oct 2011, 2:20 a.m., in response to message #19 by Dominic Richens The f prefix allows to address any key (not only A to D) to act as a shortcut. The shifts are exempt from this feature because they never act upon themselves, only as a prefix. The rule is: If a key has no predefined meaning in the context of label entry, it is translated to a row/column code. If it has, it can still be used this way by prefixing it with f. The prefix just disables the special meaning of the key such as the digits or '.'. With the new feature of command display you can always control what will be executed. This has the potential to increase the confidence in what WP 34S will execute upon a given keystroke sequence.

[ Return to Index | Top of Index ]

Go back to the main exhibit hall