|
From: | Kai Torben Ohlhus |
Subject: | [Octave-bug-tracker] [bug #57212] getappdata should search for the struct fieldname "ApplicationData" within figure objects for Matlab compatibility |
Date: | Tue, 12 Nov 2019 07:23:22 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.97 Safari/537.36 |
Update of bug #57212 (project octave): Summary: Matlab incompatibility in getappdata() when opening GUIDE-built .fig files => getappdata should search for the struct fieldname "ApplicationData" within figure objects for Matlab compatibility _______________________________________________________ Follow-up Comment #9: Agree to both of you Guillaume comment #6 and Markus comment #8. Octave is far from full GUIDE support and I don't want to address bug #44282 here. Neither we should aim to support Matlab/Octave "mishmash". Matlab compatibility is a moving target of Octave, which should *not* come at any price. While figuring out the problem of this item, the very small Matlab detail of comment #5 became apparent and I see two ways to handle the difference between fiendname "ApplicationData" (Matlab) and "__appdata__" (Octave): 1. Won't fix. Octave decided for another name. 2. Let getappdata look for both fields. Mishmash, when saving this figure and opening in Matlab again. 3. Break downwards compatibility with older Octave versions and rename that field according to Matlab. I was fine with 1. or 2. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?57212> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |