Posts: 239
Threads: 55
Joined: Sep 2006
Hi,
I apologize if this has been answered already, but I do not quite understand how [->] works in order to convert temporarily an integer from a base to another. Here are some examples :
In base 2, 11000b :
[->][blue 8] = 30o
[->][blue 16] = 18h , and I do not need to use [h] to do so.
So, What is the combination to get the base 10 conversion?
Now if I switch to base 16, how do I convert to other bases? [->] alone gives the "Eh" value, of course, but trying to use a combination like [f][->] to try to make it work, gets me an error message : "Bad mode error".
What am I doing wrong?
Thanks,
Miguel
Edited: 26 Aug 2011, 1:00 p.m.
Posts: 3,283
Threads: 104
Joined: Jul 2005
Miguel, the sequence for temporary display in another base is ->, followed by the shift key, followed by the base. As you have already found out, the f shift key is optional.
Posts: 239
Threads: 55
Joined: Sep 2006
Thanks a lot Marcus,
Now I get it.
Regards,
Miguel
Posts: 239
Threads: 55
Joined: Sep 2006
That does not seem to work in hexadecimal mode, based on what the manual says (page 8):
To use [->] in hexadecimal mode, I have to press [f] first then [->]but if I do that:
[f][->] gives a "bad mode error"
What could be the problem there?
Thanks,
Miguel
Posts: 3,283
Threads: 104
Joined: Jul 2005
This looks like a bug which needs to be fixed by us.
Edit: Found (and fixed) the bug but I need to build and commit it.
Edit again: The issue should be fixed now. In integer mode f, g and -> may be pressed in any order. In a base that takes E as a digit, f must precede ->. A second press of f after -> is not necessary.
Edited: 26 Aug 2011, 3:30 p.m.
Posts: 4,587
Threads: 105
Joined: Jul 2005
Slightly deviates from the manual, pages 57f: after ->, g may be omitted. Defined this way for quite a long time. Sorry.
Walter
Posts: 3,283
Threads: 104
Joined: Jul 2005
Quote:
pages 57f: after ->, g may be omitted
I assume it's still this way and I simply mixed it up in my comments here. Can you check with the latest emulator? I didn't change anything *after* the arrow, just the arrow detection itself which was definitely broken.