+- HP Forums (https://www.hpmuseum.org/forum)
+-- Forum: HP Calculators (and very old HP Computers) (/forum-3.html)
+--- Forum: HP Prime (/forum-5.html)
+--- Thread: choose menu fsilure in virtual prime (/thread-5481.html)
choose menu fsilure in virtual prime - ji3m - 01-08-2016 04:22 PM
I finally found the virtual prime version
Virtual Calculator Version: 2015 06 17 (8151)
There are a couple of problems:
(1) on the win10 touch screen-- the touch registration is off by half a line.
(2) More seriously, the CHOOSE function crashes the program on my major list. It mangles some strings and crashes on some. I have checked each string in the list with the memory list display. All are fine. But in CHOOSEmenu some items cause a crash and some items show a garbled string (trailing extraneous chinese characters).
This problem does not exist with the Android prime or the real calculator with the same code.
Is it possible that the paid version in the Windows Store might work? There is no version info.
RE: choose menu fsilure in virtual prime - cyrille de brébisson - 01-11-2016 05:55 AM
Hello,
Can you post the exact parameters use for the CHOOSE?
Cyrille
RE: choose menu fsilure in virtual prime - ji3m - 01-11-2016 06:20 PM
Well i prepared an examole but in the process i found the problem.
My choose list has over 500 strings (most of the prime catalog).
The rub is if any string is over 33 cgaracter some internal buffer is overrun and
the prime litterally crashes.
If i trim the stribgs to 32 characters then it works.
This size probkem does not exist in the android version or the real prime.
RE: choose menu fsilure in virtual prime - Tim Wessman - 01-11-2016 07:16 PM
(01-11-2016 06:20 PM)ji3m Wrote: My choose list has over 500 strings (most of the prime catalog).
The rub is if any string is over 33 cgaracter some internal buffer is overrun and
the prime litterally crashes.
Well, I'll look at it. Suspect I know what the problem is from your description.
EDIT: Actually, looks like was already reported a long time back on the forum here earlier and resolved. Thanks again!