Hi,
I found this:
Load a program from eeprom twice, which creates two entries in the program menu, which is exspected.
ASSIGN one entry on from the program menu to the CUSTOM MENU.
Delete one program with CLP from the program menu, which deletes both entries, which is NOT exspected.
Go to the CUSTOM menu. There is still the ASSIGNed entry, which is NOT exspected.
"Clicking" this entry produces the error message "not excistent" (or similiar).
This entry in the CUSTOM menu can only be removed by removing all entries from the CUSTOM menu.
Exspected behaviour.
Loading two programs, even if they are identical, should result in two idenpendant program instances in memory.
Removing one of it should not delete the other one.
Deleting a program from the program menu, which is assigned to the custom menu, should also delete that entry.
I did a CLALL after that to clean up the whole memory of my DM42.
Cheers!
Meino
Bug? Unresolved reference or dangling pointer (so to say)
Bug? Unresolved reference or dangling pointer (so to say)
DM 42 - SN: 00373, Firmware release v.:3.22. / DMCP 3.24. as compiled by SwissMicros
-
- Posts: 1100
- Joined: Tue May 02, 2017 5:48 pm
- Location: Netherlands
- Contact:
Re: Bug? Unresolved reference or dangling pointer (so to say)
I can't reproduce that.mcc wrote: ↑Fri Jan 26, 2018 5:44 amHi,
I found this:
Load a program from eeprom twice, which creates two entries in the program menu, which is exspected.
ASSIGN one entry on from the program menu to the CUSTOM MENU.
Delete one program with CLP from the program menu, which deletes both entries, which is NOT exspected.
The fact that you didn't expect a CUSTOM menu assignment to remain in place, after deleting the program it points to, does not make it a bug. That assignment is basically just a global XEQ. Note that you can do ASSIGN "ABC" TO 01 even when ABC doesn't exist when you do the assignment.
Are you saying that ASSIGN "" TO <key> doesn't work? I can't reproduce that.
And that is, in fact, how it works.
Correct. And that does not, in fact, happen, at least not when I try it.
Wrong.
By the way, are you going to post those HP-42S programs you said you have, which don't work in Free42, or even "kill" it? It's a bit hard for me to deal with bug reports when I don't even have the chance to even try to reproduce them.
Re: Bug? Unresolved reference or dangling pointer (so to say)
Can't reproduce it either.
Tried on a 42S, on Free42 iOS 2.0.11, and DM42 3.1, all behave exactly the same.
Werner
Tried on a 42S, on Free42 iOS 2.0.11, and DM42 3.1, all behave exactly the same.
Werner
41CV†,42S,48GX,49G,DM42,DM41X,17BII,15CE, DM15L
Re: Bug? Unresolved reference or dangling pointer (so to say)
Hi,
hmmm, can't reproduce it anymore here, too...
What may had produces this one-time-hickup on my DM42?
Cheers
Meino
hmmm, can't reproduce it anymore here, too...
What may had produces this one-time-hickup on my DM42?
Cheers
Meino
DM 42 - SN: 00373, Firmware release v.:3.22. / DMCP 3.24. as compiled by SwissMicros
Re: Bug? Unresolved reference or dangling pointer (so to say)
Let me guess ... the user??
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041
Re: Bug? Unresolved reference or dangling pointer (so to say)
Hi,
yes, of course!
But how have I managed to produce this effect?
Cheers
Meino
yes, of course!
But how have I managed to produce this effect?
Cheers
Meino
DM 42 - SN: 00373, Firmware release v.:3.22. / DMCP 3.24. as compiled by SwissMicros
Re: Bug? Unresolved reference or dangling pointer (so to say)
IIRC, there once was a "Journal of Irreproducible Effects". Please submit.
Just checked: it's called "Journal of Irreproducible Results" - anyway!
Just checked: it's called "Journal of Irreproducible Results" - anyway!
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041