Complex Lock mode for WP-34s

[Nigel (UK)]

(03-20-2015 02:25 AM)BarryMead Wrote:  I discovered a discrepancy between what the actual calculator/emulator does and what the manual says it does. In the manual it says that if "Pi" (h + EEX) is pressed immediately after CPX it puts the pi value into the Imaginary part of the number. But this is not what the actual calculator/emulator does. It ALWAYS puts the pi value into the REAL part of the number and 0 (zero) in the imaginary part, irregardless of weather you just pressed CPX or not. You cannot enter (0 + i pi) unless you exit complex lock mode and put the 0 and pi values into the X and Y registers and reenter complex lock mode.

There is another related issue that I discovered, which doesn't seem to work as one would expect. If you are entering the Real part of a number (haven't pressed CPX yet) and you select from the "const" menu (h + Enter) you get a number pair that makes sense (selected constant + i 0). Also if you start with a zero number pair (press CLx) then CPX and select a constant you get a pair that makes sense (0 + i constant).

But if you attempt to make your own CUSTOM pair (1 + i Constant) by pressing 1 CPX const you still get (0 + i const) The 1 you just entered gets overwritten by a zero. I can see why this happens, the Constants are always (Constant + i 0), or (0 + i Constant), but does it need to erase the Real part when you are entering the Complex part of the pair?

I think the manual is correct so far as pi is concerned. There are two pi functions:

• (h + pi) enters the complex number (pi + i 0), overwriting any number currently being entered. This overwriting is not what I intended; pressing (h + pi) should complete any entry in progress before entering pi. I shall correct this.
• (f + pi) does what you want, and more. So:
  
  Code:
  

  
CPX f pi ENTER
  enters 0 + i pi, and
  
  Code:
  

  
4 CPX 2 f pi ENTER
  enters 4 + i 2pi.
  

You are correct about the catalogue of constants issue. At present entering a constant either simply enters it, or overwrites the number currently being entered with (const + i 0) or (0 + i const). There is a choice here:

• If a constant is entered during the entry of a number the entry should be completed first and then the constant should be pushed onto the stack.
• If a constant is entered when a number is being entered the constant should replace the part of that number (real or imaginary) currently being entered leaving the other part unchanged.
  

Either option is possible - which would you prefer? I have a slight preference for the first option but no strong feeling.

Thank you for finding these issues. The (h + pi) problem has been present for a while without me noticing it, which surprises me. I press pi many times a day, but perhaps most often at the start of a calculation.

Nigel (UK)