Threaded Mode | Linear Mode

revwillie · 01-20-2022, 08:57 PM

I'm a little late to this pre-release party.

I can install and run the 1-19 apk. The 1-20 apk seems to crash before it runs.

I'm using an LG V60 Thinq 5G

Thomas Okken · 01-20-2022, 09:13 PM

Have you tried uninstalling and reinstalling from a new download?

Thomas Okken · 01-20-2022, 10:34 PM

OK, I'll review the code tomorrow. The changes from the previous version weren't that extensive, so whatever the problem is, can't be that hard to find, even if I can't reproduce it on my own phone or in the simulator.

Any additional information would be helpful, though, especially whatever there may be in the system log...

Thomas Okken · (This post was last modified: 01-20-2022 11:29 PM by Thomas Okken.)

I believe you, but on my phone and in the simulator, it's working fine, no crashes in sight, it works as intended and appears rock solid. I'd say that qualifies as "hard to reproduce"... I wouldn't release an app that crashed on startup on my own phone.

Thomas Okken · 01-20-2022, 11:54 PM

Perfect, thanks!

Thomas Okken · 01-21-2022, 01:26 AM

It looks like the problem occurs when the app launches without having a valid state file. That's a case I didn't test, and it has to do with having to initialize the core before loading the skin, which is the reverse of the order in which this used to happen before. When the core is initialized before the skin, care must be taken not to allow the core to call any drawing functions, since these would lead to null-pointer errors, trying to draw into bitmaps that haven't been allocated yet. I took care of this for the case where the core is initialized from a state file, but not for the case of a hard reset.

Of course I have valid state files on all my devices...

Update for all platforms first thing tomorrow!

Marco Polo · 01-21-2022, 07:53 AM

(01-21-2022 01:26 AM)Thomas Okken Wrote: It looks like the problem occurs when the app launches without having a valid state file. That's a case I didn't test, and it has to do with having to initialize the core before loading the skin, which is the reverse of the order in which this used to happen before. When the core is initialized before the skin, care must be taken not to allow the core to call any drawing functions, since these would lead to null-pointer errors, trying to draw into bitmaps that haven't been allocated yet. I took care of this for the case where the core is initialized from a state file, but not for the case of a hard reset.

Of course I have valid state files on all my devices...

Update for all platforms first thing tomorrow!

I can confirm your finding: installed latest apk on my android device without problems. But i have a valid state file

Thomas Okken · 01-21-2022, 11:30 AM

I just uploaded a new Android build. I have confirmed that (a) yesterday's build crashes on my own phone as well when run without a state file, and (b) this one doesn't.

I haven't updated the other ones since they don't seem to crash because of this issue, but they will also get the fix anyway when they are built the next time, since the fix is entirely within the core.

ggauny@live.fr · 01-21-2022, 03:07 PM

Hi AJAJA,

How can you get this in landscape. Here I don't get.

Can you give me step by step the way you have done ?

Thanks.

ggauny@live.fr · (This post was last modified: 01-21-2022 04:28 PM by ggauny@live.fr.)

Thanks a lot. I have try but impossible to do here.
I don't know where is GIMP+*layout.

Thomas Okken · (This post was last modified: 01-21-2022 06:51 PM by Thomas Okken.)

New update:

1. Variable number of columns. Only for Android and Mac (and iOS), not for Windows and Linux as those versions don't support fractional scaling.
2. The ROW+ and ROW- functions, and now also COL+ and COL-, are now in the DISP menu.
3. Implemented SKIP, CPXMAT?, and TYPE? functions. These will also be in the next Free42 release.
4. Cosmetic fixes, including the garbage in the CLALL confirmation dialog.

TYPE? can return these values:

Code:

 1: Real number

 2: Complex number

 3: Real matrix

 4: Complex matrix

 5: String

 6: List

 7: Equation

 8: Unit

 9: Directory reference

10: Program reference

11: Variable reference

Thomas Okken · 01-22-2022, 04:23 AM

Minor update:

1. Added statistics sums in a submenu under the STAT menu.
2. Fixed NULL being displayed on menu keys that should be blank, when the display is showing more than 22 columns.

Werner · 01-22-2022, 07:46 AM

(01-21-2022 06:46 PM)Thomas Okken Wrote: 3. Implemented SKIP, CPXMAT?, and TYPE? functions. These will also be in the next Free42 release.

Will SKIP take an argument? Eg. SKIP 3
Werner

Didier Lachieze · 01-22-2022, 08:32 AM

On the latest Android app, in program mode if you type for example ‘1 ENTER’ the value 1 is replaced by another value which seems related to the previous entered number.

Thomas Okken · 01-22-2022, 09:28 AM

(01-22-2022 07:46 AM)Werner Wrote:
(01-21-2022 06:46 PM)Thomas Okken Wrote: 3. Implemented SKIP, CPXMAT?, and TYPE? functions. These will also be in the next Free42 release.

Will SKIP take an argument? Eg. SKIP 3
Werner

No, it just skips one line. I added it for the specific purpose of negating the sense of tests that have no convenient inverse, like REAL? or HEAD etc.

(01-22-2022 08:32 AM)Didier Lachieze Wrote: On the latest Android app, in program mode if you type for example ‘1 ENTER’ the value 1 is replaced by another value which seems related to the previous entered number.

Yes, it looks like the index into the command line isn't being reset to zero. I wonder how I managed to break that, very odd...

Thomas Okken · 01-22-2022, 10:12 AM

(01-22-2022 09:28 AM)Thomas Okken Wrote:
(01-22-2022 08:32 AM)Didier Lachieze Wrote: On the latest Android app, in program mode if you type for example ‘1 ENTER’ the value 1 is replaced by another value which seems related to the previous entered number.

Yes, it looks like the index into the command line isn't being reset to zero. I wonder how I managed to break that, very odd...

Fixed!

Didier Lachieze · 01-22-2022, 11:10 AM

(01-20-2022 07:28 PM)Thomas Okken Wrote: New update:

1. Resizable display. Use the ROW+ and ROW- functions.
(They're under CATALOG -> DISP. I should probably put them somewhere more obvious, like under the DISP menu...)

This works well !

One thing in big screen mode I would like to have is a permanent row of soft keys to avoid the stack moving up and down every time we enter or exit a menu. By default the CUSTOM menu could displayed.

Vincent Weber · (This post was last modified: 01-22-2022 11:20 AM by Vincent Weber.)

(01-22-2022 10:12 AM)Thomas Okken Wrote:
(01-22-2022 09:28 AM)Thomas Okken Wrote: Yes, it looks like the index into the command line isn't being reset to zero. I wonder how I managed to break that, very odd...

Fixed!

You can make the CUSTOM menu (or any menu) sticky just by pressing SHIFT + CUSTOM twice. Even on the original 42S. I learnt this recently Smile

Thomas Okken · 01-22-2022, 11:34 AM

CUSTOM is always sticky... I think what Didier is referring to is showing CUSTOM whenever there would otherwise be no menu. There is an alternate DM42 firmware that works like that, but I've never looked into it myself.

Vincent Weber · 01-22-2022, 11:35 AM

(01-22-2022 11:34 AM)Thomas Okken Wrote: CUSTOM is always sticky... I think what Didier is referring to is showing CUSTOM whenever there would otherwise be no menu. There is an alternate DM42 firmware that works like that, but I've never looked into it myself.

Yes indeed. I stand corrected.