Calculator Community > HP Calculators

HP Prime CAS: Error reports, request, etc :

<< < (2/2)

Adriweb:

--- Quote from: DJ Omnimaga on July 22, 2013, 12:41:13 pm ---Yeah IIRC for the calc itself they're under NDA until September, as does anyone else who received a sample of the calc, so they might not be allowed to showcase it until then. Of course, some people already did, but it's best that others respect HP's wishes to not show things before they want you to, else in the future they will feel more relunctant about giving people the chance to test samples of their products.

--- End quote ---
^ This exactly.


Edit : btw, I "posted" to this forum but my message apparently didn't get past validation...

DJ Omnimaga:
I don't have time to post there, but there is a bug I found right now:

If you try using RECT_P with a color value other than the RGB(#,#,#) format, such as a decimal number, for example, it will act as the black color. However, with PIXON_P it works fine.

So for example, this will slowly fade the screen to black:

--- Code: ---EXPORT fadein()
BEGIN
FOR C FROM 0 TO 3 DO
FOR X FROM 0 TO 319 DO
FOR Y FROM 0 TO 239 DO
INT(GETPIX_P(X,Y)/2)▶P;
PIXON_P(X,Y,P);
END;
END;
END;
END;
--- End code ---

However, if you try using RECT_P instead for any reason (such as wanting to pixelate the screen as it fades in):


--- Code: ---EXPORT fadein2()
BEGIN
FOR C FROM 1 TO 4 DO
2^C▶D;
FOR X FROM 0 TO 319 STEP D DO
FOR Y FROM 0 TO 239 STEP D DO
INT(GETPIX_P(X,Y)/2)▶P;
RECT_P(X,Y,X+D,Y+D,P,P);
END;
END;
END;
END;

--- End code ---

Then the pixels will immediately become black without fading in.

This is definitively a bug, since PIXON accepts non-RGB color format, yet RECT doesn't.

Navigation

[0] Message Index

[*] Previous page