Apologies if this has been asked before; the forum's search feature won't let me search for such "common terms".
Is there any way to convert/extract from a DM42 state file so that it may be used with Free42, e.g. on desktop, Android, etc?
thanks very much.
state file sharing
state file sharing
Cambridge, UK
41CL/DM41X 12/15C/16C DM15/16 17B/II/II+ 28S 42S/DM42 32SII 48GX 50g 35s WP34S PrimeG2 WP43S/pilot
Casio, Rockwell 18R
41CL/DM41X 12/15C/16C DM15/16 17B/II/II+ 28S 42S/DM42 32SII 48GX 50g 35s WP34S PrimeG2 WP43S/pilot
Casio, Rockwell 18R
-
- Posts: 1100
- Joined: Tue May 02, 2017 5:48 pm
- Location: Netherlands
- Contact:
Re: state file sharing
Prior to release 2.5, the Free42 state file format was only compatible with itself. Something as innocent as changing compilers or compiler settings could introduce incompatibilities, and moving state files between platforms was also impossible.
In 2.5 I changed the state file reading and writing logic to eliminate these issues, and the state files can now be exchanged between Free42 instances running on different platforms (and compiler quirks should not cause problems any more, either).
Once the DM42 firmware is merged with the latest Free42, it could also become state-file-compatible, though with a caveat: the DM42 state contains elements that aren't present in the Free42 state, and since the Free42 state file format makes no explicit provision for optional sections, any DM42-specific fields would have to be added at the end, after the closing "24kF<version>" marker, where Free42 will ignore them, and when reading a state file, the DM42 should likewise be prepared to encounter EOF after that marker, and fill in default values for all DM42-specific fields when that happens.
In 2.5 I changed the state file reading and writing logic to eliminate these issues, and the state files can now be exchanged between Free42 instances running on different platforms (and compiler quirks should not cause problems any more, either).
Once the DM42 firmware is merged with the latest Free42, it could also become state-file-compatible, though with a caveat: the DM42 state contains elements that aren't present in the Free42 state, and since the Free42 state file format makes no explicit provision for optional sections, any DM42-specific fields would have to be added at the end, after the closing "24kF<version>" marker, where Free42 will ignore them, and when reading a state file, the DM42 should likewise be prepared to encounter EOF after that marker, and fill in default values for all DM42-specific fields when that happens.
Re: state file sharing
thanks very much Thomas, I thought that might be the case.
In that case, if any SM folk are reading, please consider this a request to add such functionality.
An alternative, or short-term workaround (once the DM42 has Free42 2.5), might be a separate tool to convert between the two formats, optionally using an existing DM42 state file as a template from which to take the DM42-specific values.
thanks again.
In that case, if any SM folk are reading, please consider this a request to add such functionality.
An alternative, or short-term workaround (once the DM42 has Free42 2.5), might be a separate tool to convert between the two formats, optionally using an existing DM42 state file as a template from which to take the DM42-specific values.
thanks again.
Cambridge, UK
41CL/DM41X 12/15C/16C DM15/16 17B/II/II+ 28S 42S/DM42 32SII 48GX 50g 35s WP34S PrimeG2 WP43S/pilot
Casio, Rockwell 18R
41CL/DM41X 12/15C/16C DM15/16 17B/II/II+ 28S 42S/DM42 32SII 48GX 50g 35s WP34S PrimeG2 WP43S/pilot
Casio, Rockwell 18R
Re: state file sharing
As I already stated (see my comments of Wed Oct 30 in viewtopic.php?f=2&t=1816&start=470), I completely agree with this official request of state file sharing possibilities between DM42 and Free42 (or at least to access a simple method to convert between the two formats as suggested by cdmackay). Could this request be considered and judge for its feasability and eventual timetable? Thanks for your answer.
DM42 SN: 03090
HP-29C, HP-41C, HP-15C, HP-33s, HP-35s, WP 34S, Free42, DM42
(Fortran, C++, Mathematica, Maple, Python, …) Physics aficionado
HP-29C, HP-41C, HP-15C, HP-33s, HP-35s, WP 34S, Free42, DM42
(Fortran, C++, Mathematica, Maple, Python, …) Physics aficionado
Re: state file sharing
I concur with this request. Personally, I'd put it in the "nice to have" folder though.
WP43 SN00000, 34S, and 31S for obvious reasons; HP-35, 45, ..., 35S, 15CE, DM16L S/N# 00093, DM42β SN:00041
Re: state file sharing
Thanks Mr. Walter, and let's hope that others will join our request.
DM42 SN: 03090
HP-29C, HP-41C, HP-15C, HP-33s, HP-35s, WP 34S, Free42, DM42
(Fortran, C++, Mathematica, Maple, Python, …) Physics aficionado
HP-29C, HP-41C, HP-15C, HP-33s, HP-35s, WP 34S, Free42, DM42
(Fortran, C++, Mathematica, Maple, Python, …) Physics aficionado