Post Reply 
[BUG(ish)] Text entry in text fields in RPN mode
04-02-2014, 10:49 PM
Post: #1
[BUG(ish)] Text entry in text fields in RPN mode
While editing any of the text input fields that accept algebraic input in apps (e.g. Function or Advanced Graphing), if you hit Edit then press SIN, you will get:

'SIN()'

with the cursor positioned between the parentheses (as expected).
If, however you don't press Edit and instead hit SIN straight away, you will get:

SIN<space>

(no single quotes, no parentheses, extra space).
This, of course, only happens if Home is in RPN mode. But that shouldn't matter, because Edit defaults into algebraic entry via the single quotes. Typing without hitting Edit should too, in this context, methinks.
Find all posts by this user
Quote this message in a reply
04-04-2014, 01:07 PM (This post was last modified: 04-04-2014 01:08 PM by Marcus von Cube.)
Post: #2
RE: [BUG(ish)] Text entry in text fields in RPN mode
(04-02-2014 10:49 PM)orcinus Wrote:  This, of course, only happens if Home is in RPN mode. But that shouldn't matter, because Edit defaults into algebraic entry via the single quotes. Typing without hitting Edit should too, in this context, methinks.
I think it's intended behavior. Without the quotes you're in RPN mode. To get SIN(X) you will have to input 'X' (with the quotes!) and hit SIN. Without the quotes around X, the numerical value of X will be used instead because X is an 'always there' type of object, not a symbolic one.

Marcus von Cube
Wehrheim, Germany
http://www.mvcsys.de
http://wp34s.sf.net
http://mvcsys.de/doc/basic-compare.html
Find all posts by this user
Quote this message in a reply
04-04-2014, 01:44 PM
Post: #3
RE: [BUG(ish)] Text entry in text fields in RPN mode
I was wrong (shouldn't post late at night without checking on the actual calculator first), the second example actually should've said:

'SIN '

So no parentheses, extra space, but single quotes (i.e. it defaults to algebraic input, but actually plops the RPN syntax function in there).

I'm pretty sure it's intended behaviour too (hence the "ish" in the thread subject), but it's a bit inconsistent from a UI/UX point of view.
Find all posts by this user
Quote this message in a reply
Post Reply 




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