Post Reply 
newRPL - build 1255 released! [updated to 1282]
09-07-2019, 08:54 PM
Post: #581
RE: newRPL - build 1255 released! [updated to 1282]
hi, just starting to use newRPL again, after a while away (no time).

I run my Android phone (Samsung Note 10+) in high-resolution mode (3040x1440); in this mode, the newRPL skin doesn't fit the screen: it's too wide. The skin does look OK in the lower res mode (2280x1080). Would you be able to provide a skin that works for the high res mode, please?

Also, when the app starts, there's a popup: "Detected problems with API compatibility". The phone runs Android 9.

Finally, I note that File->Exit doesn't actually exit. It pops up the prompt "do you want to save" twice, but doesn't actually exit.

Known issues?

thanks very much indeed.

Cambridge, UK
41CL, 12C/15C, DM15/16, 71B, 17B, 28S, DM42, 48GX, 17bII+, 50g (& newRPL), 35s, 30b (WP 34S), Prime G2
& Casios, Rockwell 18R :)
Find all posts by this user
Quote this message in a reply
09-08-2019, 12:29 AM
Post: #582
RE: newRPL - build 1255 released! [updated to 1282]
(09-07-2019 08:54 PM)cdmackay Wrote:  hi, just starting to use newRPL again, after a while away (no time).

I run my Android phone (Samsung Note 10+) in high-resolution mode (3040x1440); in this mode, the newRPL skin doesn't fit the screen: it's too wide. The skin does look OK in the lower res mode (2280x1080). Would you be able to provide a skin that works for the high res mode, please?

Also, when the app starts, there's a popup: "Detected problems with API compatibility". The phone runs Android 9.

Finally, I note that File->Exit doesn't actually exit. It pops up the prompt "do you want to save" twice, but doesn't actually exit.

Known issues?

thanks very much indeed.

There's one and only one skin, which gets stretched to fill up the screen (turn your phone 90degrees and see for yourself). The problem is I believe Samsung reports a fake screen size, reserving some size for the edge notifications in some models, and this confuses the QT framework. There's nothing I can fix, I'll upgrade to the latest QT version for the next release to see if they fix that eventually.

Exit also relies on the QT framework. In Android there's no such thing as exiting an app, you just switch to another one so it doesn't seem to work. Just don't use exit from the menu for the time being.

You are the first to report that API compatibility problem, newRPL is compiled to run on Android 5.0 and up. I'll update the SDK for the next build, to see if they solved whatever that is.

Thanks for the report, I wish I had better solutions...
Find all posts by this user
Quote this message in a reply
09-08-2019, 12:40 AM (This post was last modified: 09-08-2019 12:40 AM by Claudio L..)
Post: #583
RE: newRPL - build 1255 released! [updated to 1282]
(09-07-2019 04:02 PM)The Shadow Wrote:  
(09-07-2019 08:40 AM)JoJo1973 Wrote:  Well, angles and gauge units are different cans of worms,

They aren't, though. In addition to newRPL's angle objects, there are also angle units.

Though it's true that angle objects should be handled properly by transcendental functions too, just as units are.

So we all agree: Unit objects need to be converted to their base units and simplified to see if they become non dimensional. This will also handle units of angles correctly since their base unit is the radian (angle objects already convert to radians automatically, that discussion is only a few pages up in this thread). If the units are NOT non-dimensional, then it shall throw an error of "Inconsistent units".
The result of the functions shall be a number, without any units.

Finally, regarding temperature units, newRPL already distinguishes temperature from change of temperature, and if everything works as intended, the conversion to absolute temperature is automatic during UBASE.
Find all posts by this user
Quote this message in a reply
09-08-2019, 12:44 AM
Post: #584
RE: newRPL - build 1255 released! [updated to 1282]
Sounds good to me, Claudio! Go for it.
Find all posts by this user
Quote this message in a reply
09-08-2019, 05:18 PM
Post: #585
RE: newRPL - build 1255 released! [updated to 1282]
(09-08-2019 12:29 AM)Claudio L. Wrote:  There's one and only one skin, which gets stretched to fill up the screen (turn your phone 90degrees and see for yourself). The problem is I believe Samsung reports a fake screen size, reserving some size for the edge notifications in some models, and this confuses the QT framework. There's nothing I can fix, I'll upgrade to the latest QT version for the next release to see if they fix that eventually.

Exit also relies on the QT framework. In Android there's no such thing as exiting an app, you just switch to another one so it doesn't seem to work. Just don't use exit from the menu for the time being.

You are the first to report that API compatibility problem, newRPL is compiled to run on Android 5.0 and up. I'll update the SDK for the next build, to see if they solved whatever that is.

Thanks for the report, I wish I had better solutions...

Thanks for the detailed reply, Claudio. Indeed, they're not big issues — I never use Exit anyway, as you say — just wanted to report them just in case you weren't aware.

thanks again!

Cambridge, UK
41CL, 12C/15C, DM15/16, 71B, 17B, 28S, DM42, 48GX, 17bII+, 50g (& newRPL), 35s, 30b (WP 34S), Prime G2
& Casios, Rockwell 18R :)
Find all posts by this user
Quote this message in a reply
09-17-2019, 04:08 PM
Post: #586
RE: newRPL - build 1255 released! [updated to 1282]
Claudio, a question about PI from the Constants library and PI0: the latter returns PI at double the current precision, but I recall having read that PI and 'e' always return 2000+ digits of precision.

Am I right? If so, what's the point in still having PI0 around then? Do I miss something?
Find all posts by this user
Quote this message in a reply
09-18-2019, 02:11 PM
Post: #587
RE: newRPL - build 1255 released! [updated to 1282]
(09-17-2019 04:08 PM)JoJo1973 Wrote:  Claudio, a question about PI from the Constants library and PI0: the latter returns PI at double the current precision, but I recall having read that PI and 'e' always return 2000+ digits of precision.

Am I right? If so, what's the point in still having PI0 around then? Do I miss something?

The only reason is I still didn't take the time to remove pi0. It was a "hack of the moment" to have the constant pi before there were constants implemented in newRPL. It's not a constant but a command, and cannot be used in symbolics. But I couldn't debug angle conversions and angle objects without having a convenient pi to do some hand calculation checks.
So no, there's no point and it will be removed at some point.
Find all posts by this user
Quote this message in a reply
10-11-2019, 10:19 PM
Post: #588
RE: newRPL - build 1255 released! [updated to 1282]
Hello Claudio,

what's the meaning of system flags -12, -45, -46 and -47?
Find all posts by this user
Quote this message in a reply
10-14-2019, 08:54 PM
Post: #589
RE: newRPL - build 1255 released! [updated to 1282]
(10-11-2019 10:19 PM)JoJo1973 Wrote:  Hello Claudio,

what's the meaning of system flags -12, -45, -46 and -47?

Those flags belong in the newRPL UAUR (Ultra-Advanced User Reference):

Flag -12 is set/cleared every time the user presses a key in the soft menus.
It's cleared if the pressed key was in menu 1 (top), set if it was in menu 2.
It affects the commands xxxLST and xxxOTHR:
TMENU: Modifies the "Active" menu (active menu is controlled by flag -11, usually (-flag clear-) it's the top one).
TMENULST / TMENUOTHR: They do TMENU, but the former uses the menu in which the user pressed last, while the latter changes the menu the user did NOT press last (a.k.a the "other" menu). They are meant to be used to bring up menus within menu handlers. For example, a menu handler may use TMENUOTHR to open a custom sub-menu in the other menu.

RCLMENU / RCLMENULST/RCLMENUOTHR: Same as RCLMENU, but following the same logic.
MENUBK / MENUBKLST / MENUBKOTHR: Brings up the previous menu for all 3 cases.


Flag -45 = DONEXTCUSTOMKEY
This flag is cleared right before entering a custom (user) key handler. Normal case is that the key handler will consume the key press, once the handler executes, no other handler will be used. However, you can "chain" handlers: let's say you want to count how many times the user presses the number "4", so you create a custom key handler that increments a global variable and you ASNKEY to number 4. But you want the "4" key to still be functional, so you set this flag, and the system will continue looking for additional custom handlers (previously installed for that same key). This way your handler is completely transparent. There's no limit on the number of handlers you can have for the same key.

Flag -46 = DODEFAULTKEY
Similar to -45, but this one is cleared before the first custom key handler is executed (there could be more than one as per chain execution above). Once all the custom key handlers finished executing, if this flag is set, the system will execute the standard default handler for that key. In other words, if any one of the custom handlers decided that the key should do the default behavior, setting this flag achieves it. In the example above, for the number "4" to be functional, your handler would have to set both flags, -45 and -46. The user would never know that the key was being logged.

Flag -47 = Disable auto execution of programs sent via USB. By default, sending a program with USBSEND will execute it automatically in the remote calculator. This flag disables that behavior. When data is received and this flag is set, the "Rx" signal will show in the status area until USBRECV is executed to pick up the data. In general, it's best to leave this flag clear (auto-receive enabled), since newRPL Desktop needs it to communicate with the calculator to establish the connection (it retrieves newRPL version, serial number for selection, and is also needed to run the firmware update process). If you don't want to execute a program, simply run USBRECV on the remote before sending it (which incidentally can be sent from the remote!).
Find all posts by this user
Quote this message in a reply
Post Reply 




User(s) browsing this thread: 1 Guest(s)