Thanks!

Yes, I should be more clear or at least keep it simple.  I love the calculator and I have high hopes for continued updates/fixes/improvements, and my optimism comes mainly from seeing TW's comments here and on MoHPC.

The Bug and/or request is that the K_Home user key override doesn't work when in the home screen--the HOME key retains it's usual effect of "nothing" from there, but if you are on another screen, for example the home-settings screen, then the user key override program DOES run.  This seems exactly backwards from (possibly) intended function.  If not on the home screen I could agree that the HOME key should take you there and I could understand making it difficult or impossible to user-override this function.  But once on the home screen, the HOME key doesn't do anything, so it would be useful/reasonable to override it's function there.

KEY K_Home()
BEGIN
  IF Entry==2 THEN Entry:=0; ELSE Entry:=2; END;
  STARTVIEW(-8,0);
  STARTVIEW(-1,1);
  RETURN 5;
END;
This seems to not work when I want it to (while on the home screen), but does work when I don't want it to (when pushing HOME to return from home-settings).

I am unsure if Tim Wessman and others are still reading this thread since most of the bugs are reported on MoHPC, but I ran into another issue:

In the connectivity kit, after opening the emulator, it now shows an error at the bottom of the screen saying "Size error (too big) - Message dropped", and in the emulator content list, my engine3D2 program (which is 62 KB on-calc and in the emulator) always remains missing, while on the emulator it shows up. I am unsure if it's because I have close to 200 KB of stuff on my calc or if it's because the Connectivity kit is unable to display programs larger than 50-60 KB?

By the way, the source code in text format (pasted in Notepad) is 442 KB.


Also, I find it strange that this program is 62 KB, while my previous version called engine3D was 47 KB despite having about 4-5 times fewer GROB data . Are you sure that the size of programs displayed in the program menu on the calc is right?

Yeah I would like an universal copy/paste too, same for the note-taking stuff.

By the way, another issue that I noticed with the calc is that the link port seems kinda loose. I am a bit concerned about that. I hope it doesn't break after a while


EDIT: FATAL BUG: In certain cases it seems (perhaps large programs or heavy DIMGROB/BLIT usage?), if you connect the calc to the computer, some programs might be messed up during runtime. For example, in the following screenshot (which I scaled down to half its size):



1) If I connect the cable before the program is ran, then the 3D blocks will not appear at all and the FPS counter will say 90-100 (I use the TICK command for it btw). Only the background will appear behind.
2) If I connect the cable while the program is running, then the FPS counter text will start displaying garbage.
3) In one occasion, the screen messed up then the calc froze, requiring pushing the small reset button with a needle.

My USB port is loose too.
I really hope HPs new line has a long and prosperous future. Lots of things can be improved upon.

Another error I've gotten when manipulating the backup file is that it can turn most of my notes into 'Asian' characters.

Bug:
When programming with the MOUSE() function, with two pointers going (two fingers on the screen), if you pick up the finger for the first pointer, then suddenly both pointers are at the location of the second finger, and then when you pick up the second finger, the second pointer often gets "stuck", where the mouse function is returning data for the second pointer only, first list is empty, and this goes on indefinitely, with nothing touching the screen, until you touch the screen again.  This happens regularly when you (1) touch finger1, (2) touch finger2, (3) lift finger1, (4) lift finger2.  I narrowed it down to when you do steps (3) and (4) quickly, as if pulling both finger off at the same time, but second finger a bit behind.  The closer together the lifts are the more likely it is to stick.

It seems to be related to the fact that the second pointer gets "taken over" by the first pointer when you lift the first finger, that is, when you lift the first finger leaving the second finger down, the data coming in the first list from MOUSE() suddenly become the coordinates of the second finger, and the data coming in the second list "stick" at wherever the point was, and when both fingers are lifted then both lists become empty.  I'm sure this is known and maybe considered normal, but I wanted to point out about the second pointer becoming more permanently "stuck" if you remove the fingers quickly.

I guess it's easy enough to just ignore the second list from MOUSE() if the first list is empty, but I have to say the touch screen with the two independent pointers is really fun to program with because it works so well, and the possibilities seem endless, so it's a shame that the two pointers are not quite "independent".

Let me know if anyone wants more information.

Phil

Edit:  I was thinking about this more, and I realized it isn't too hard to recognize when the first pointer suddenly jumps to the location of the second, and take care of the issue that way, but I do think it's a bug and could more easily be fixed in the code for the MOUSE function itself.

HP Prime - This is ridiculous
Message #1 Posted by Michael de Estrada on 25 Nov 2013, 2:25 p.m.
For the third time I've had to re-format the flash drive on the Prime to recover the OS. This time the settings screens locked up and I couldn't make any changes. When I did the restore from my pc with the connectivity kit, I got the old Apps key reboot routine, so I had to re-format again. Next I transferred some programs from my Emulator to the Prime, but the Apps transfer caused memory to explode, so I'll have to type them all back in on the Prime, which I'm not about to do.
But it gets better, since now programs that used to work no longer do, despite all settings being the same. CAS solve won't work in a program despite working fine previously, so basically the program is now worthless.
In short, this calculator is a nightmare, and possibly the worst product ever to wear the hp logo. I may continue working with the Emulator, but the physical Prime is going into permanent storage.

Do you need a good laugh? Look it up!
http://www.hpmuseum.org/cgi-sys/cgiwrap/hpmuseum/forum.cgi?read=256942#256942

Yeah, let's hope it's an isolated case, but i don't think so, unfortunately for many!

This one's more a suggestion than a bug: Despite being in CAS mode, using the Define box only creates 'normal' functions, not xcas ones.

Another bug: This program errors with "Invalid input" when I hit ENTER, yet works fine in debug mode:

Code: [Select]

EXPORT CURSOR()
BEGIN
LOCAL X,Y,K,C,P;
0▶X;0▶Y;0▶P;
WHILE 1 DO
 //WAIT()▶K;
 WAIT(.05);
 IF ISKEYDOWN(4) THEN
  RETURN {X,Y};
 END;
 IF ISKEYDOWN(2) THEN
  GETPIX_P(G0,X,Y)▶C;
  BITNOT(C)▶C;
  PIXON_P(G0,X,Y,C);
  Y-1▶Y;
  GETPIX_P(G0,X,Y)▶C;
  BITNOT(C)▶C;
  PIXON_P(G0,X,Y,C);
 END;
 IF ISKEYDOWN(12) THEN
  GETPIX_P(G0,X,Y)▶C;
  BITNOT(C)▶C;
  PIXON_P(G0,X,Y,C);
  Y+1▶Y;
  GETPIX_P(G0,X,Y)▶C;
  BITNOT(C)▶C;
  PIXON_P(G0,X,Y,C);
 END;
 IF ISKEYDOWN(7) THEN
  GETPIX_P(G0,X,Y)▶C;
  BITNOT(C)▶C;
  PIXON_P(G0,X,Y,C);
  X-1▶X;
  GETPIX_P(G0,X,Y)▶C;
  BITNOT(C)▶C;
  PIXON_P(G0,X,Y,C);
 END;
 IF ISKEYDOWN(8) THEN
  GETPIX_P(G0,X,Y)▶C;
  BITNOT(C)▶C;
  PIXON_P(G0,X,Y,C);
  X+1▶X;
  GETPIX_P(G0,X,Y)▶C;
  BITNOT(C)▶C;
  PIXON_P(G0,X,Y,C);
 END;
 IF ISKEYDOWN(30) THEN
  REPEAT
   MOUSE()▶P;
   P[1]▶P;
  UNTIL P[5]==#1;
  B→R(P[1])▶X;
  B→R(P[2])▶Y;
 END;
 END;
END;
END;


Not sure if this was ever addressed, but the reason you are getting different behavior is due to the fact that debugging necessarily means you touched the screen (you pressed "DEBUG" on the menu). The system processes all touches and signifies that it has finished handling the touch event via the MOUSE command. So when you call MOUSE, it actually returns the last touch -- you pressing the DEBUG menu option -- along with the signal that it was handled. However, when you run it from the command line (and presumably have not touched the screen), then MOUSE returns two empty lists -- which would result in invalid input later on when you try to pull elements out of empty lists.