[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #37645] "set" function not properly working wi
From: |
Pantxo Diribarne |
Subject: |
[Octave-bug-tracker] [bug #37645] "set" function not properly working with prop/val structure input. |
Date: |
Mon, 29 Oct 2012 11:18:26 +0000 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20100101 Firefox/16.0 |
Follow-up Comment #3, bug #37645 (project octave):
Well I have already reached my c++ limits :-) ... I dont't even understand
when/how updtate_XXX functions are called.
ML does update the "activepositionproperty", depending on the order in which
the PV structure fields where stored :
plot (1:10)
legend ('toto')
prp.position = get (gca, 'position');
prp.outerposition = get (gca, 'outerposition');
prp.activepositionproperty = get (gca,'activepositionproperty');
figure ();ax = axes (); set (ax, prp)
yields the same properties as the original,
...
prp.activepositionproperty = get (gca,'activepositionproperty');
prp.position = get (gca, 'position');
prp.outerposition = get (gca, 'outerposition');
figure ();ax = axes (); set (ax, prp)
yields "outerposition" as "activepositionproperty",
...
prp.activepositionproperty = get (gca,'activepositionproperty');
prp.outerposition = get (gca, 'outerposition');
prp.position = get (gca, 'position');
figure ();ax = axes (); set (ax, prp)
and this yieds to "position" as "activepositionproperty".
As far as I understand (thus not really far) I think avoiding the alphbetical
sorting in graphics_object::set (const octave_map& m) would lead to the same
behaviour in octave.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?37645>
_______________________________________________
Message posté via/par Savannah
http://savannah.gnu.org/