[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #57212] Figure import should map field name "A

From: Kai Torben Ohlhus
Subject: [Octave-bug-tracker] [bug #57212] Figure import should map field name "ApplicationData" to "__appdata__" for Matlab compatibility.
Date: Tue, 12 Nov 2019 21:21:42 -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: getappdata should search for the struct fieldname
"ApplicationData" within figure objects for Matlab compatibility => Figure
import should map field name "ApplicationData" to "__appdata__" for Matlab


Follow-up Comment #11:

> I'm not sure we can save .fig files in Octave that can be opened in Matlab.
Please, correct me if I'm wrong.

No correction is necessary.  At work, I just tried again without success. 
When using

>> h = openfig ("TestGUI.fig");
>> savefig (h, "TestGUI_octave.fig");

the latter one cannot be opened with MATLAB R2019a.  Same holds for
hgsave-hgload with the options "-binary", "-text", "-v7", and "-v6".

You are right, Markus.  Doing the mapping in the import functions seems
smarter to me too.  The error in getappdata is just a result of an
incompatible naming convention.  The interface between Matlab and Octave are
the import functions in this case.

Pantxo also touched this struct field recently in bug #57211 basically to hide


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]