Incompatible Encoding on Old Engauge Files

[kylesower]

Using your DumpGraphAndScreenCoordinates.py script, I discovered that old Engauge files have a strange encoding that prevents them from being read correctly. I've attached an example file (though you'll have to change the file extension from .txt to .dig). Sometimes it is possible to open the file in a newer version of Engauge and overwrite the save, which resolves the encoding issue. However, it would be nice to have a faster conversion that is scriptable for a large number of files.

1952_bro_zem-134 Fig_2_superconducting_(magnetic_field_off).txt

[markummitchell]

The old format was binary. You are right - the scripts should be upgraded to work with that old format. I will modify the file reading code to support the old format. It should take about a week. Would that time frame work for you?

[markummitchell]

Should be working now, but to test it you will need the upgraded python script and the new Engauge executable which has not been released yet. I have a Windows 64 bit msi installer with all that you need. However, github will not let me copy that into any of these posts so you will need to download from https://drive.google.com/drive/folders/14b1-hX9pzVrkNVVtjdn5Hlf0rlq2DPzm?usp=sharing. For safety I have locked the download file down, and you can also check that the file size is 19,582,976 bytes.

[kylesower]

Just tested it - works great. I just had to change the directory in the upgrade function to point to the new Engauge install. Thank you!

[markummitchell]

The script now offers some help for setting the path.