1 Pages (6 items)
XMCD File Type plugin - XMCD File Type plugin - Messages
#1 Posted: 10/12/2021 1:48:43 PM
Hi all,
I have a lot of old .xmcd files to convert to .sm, but I encounter problems when opening almost all of them, unless I save them in XMCD 12 or 13 and I remove images.
I spent some time to debug the plugin, and I found this:
- images are not always represented as string in base64
- only if format XMCD > 13: there's hell with indeces in function MergeManyArrayPostfix in OpenSaveXMCD.cs - often, index for 'value' array is less than 0.
I have some questions about this plugin:
- is advised version of XMCD 12 or 13?
- if there's limitation on format, can not supported format be blocked?
thanks in advance for such info
I have a lot of old .xmcd files to convert to .sm, but I encounter problems when opening almost all of them, unless I save them in XMCD 12 or 13 and I remove images.
I spent some time to debug the plugin, and I found this:
- images are not always represented as string in base64
- only if format XMCD > 13: there's hell with indeces in function MergeManyArrayPostfix in OpenSaveXMCD.cs - often, index for 'value' array is less than 0.
I have some questions about this plugin:
- is advised version of XMCD 12 or 13?
- if there's limitation on format, can not supported format be blocked?
thanks in advance for such info
#2 Posted: 10/13/2021 8:11:08 AM
Hello johnnyontheweb,
That plugin is open to improvements, the main problem is that you should be familiar with both programs to do something.
In general, if there are multiple data types for the same objects would be better to detect the type, then develop alternative functions to read the data, otherwise read a placeholder, nothing, or throw an error. I wouldn't block the entire format just because the indices, better to have something to start from than nothing.
That plugin is open to improvements, the main problem is that you should be familiar with both programs to do something.
In general, if there are multiple data types for the same objects would be better to detect the type, then develop alternative functions to read the data, otherwise read a placeholder, nothing, or throw an error. I wouldn't block the entire format just because the indices, better to have something to start from than nothing.
If you like my plugins please consider to support the program buying a license; for personal contributions to me: paypal.me/dcprojects
#3 Posted: 10/13/2021 10:08:07 AM
WroteI wouldn't block the entire format just because the indices, better to have something to start from than nothing
I completely agree on that, the point is nothing except text regions is read in most cases.
A message warning the user to give XMCD <= 13 as input would definitely save a lot of time in trials.
Consider, as a sample, the 2 files attached (they are the same file, with 2 different XMCD formats):
inertias.xmcd (76 KiB) downloaded 116 time(s).
inertias13.xmcd (60 KiB) downloaded 95 time(s).
#4 Posted: 10/14/2021 5:58:38 AM
WroteConsider, as a sample, the 2 files attached (they are the same file, with 2 different XMCD formats):
inertias.xmcd (76 KiB) downloaded 116 time(s).
inertias13.xmcd (60 KiB) downloaded 95 time(s).
Thank you very much, this might help a lot! I'll try to improve the plugin as soon as I can.
If you like my plugins please consider to support the program buying a license; for personal contributions to me: paypal.me/dcprojects
#5 Posted: 10/14/2021 6:08:49 AM
Wrote
Thank you very much, this might help a lot! I'll try to improve the plugin as soon as I can.
You're welcome - please keep in mind that inertias is in format XMCD>13, the other in XMCD = 13.
And please do not comment calculations on principal axes because they're not always right :d
#6 Posted: 3/2/2022 2:55:48 PM
I'm looking forward to see if there's improvements for XMCD plugin, I really need it.
I just want to tell that I noticed another problem in this plugin: if the original .xmcd file has repeted definitions (es. a:=1 more than once), the plugin removes all the occurrences and in the resulting file the variable is lost (no "a" defined at all).
I just want to tell that I noticed another problem in this plugin: if the original .xmcd file has repeted definitions (es. a:=1 more than once), the plugin removes all the occurrences and in the resulting file the variable is lost (no "a" defined at all).
1 Pages (6 items)
-
New Posts
-
No New Posts