<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hello Clément,<br>
<br>
Le 14/03/2016 11:10, Clément David a écrit :<br>
</div>
<blockquote
cite="mid:1457950224.2472.39.camel@scilab-enterprises.com"
type="cite">
<pre wrap="">Hello Samuel,
If I understand correctly, it might be sufficient to set `gce` on when a graphical object is
selected (not edited but just selected), no ?</pre>
</blockquote>
<ul>
<li>Driving the focus for the data curve editor of a given figure:
If its data curve editor in "on", AND<br>
</li>
<ul>
<li>if gce() is a polyline in the considered figure, then,
indeed, the default edited curve could be set to gce(). This
would allow to set the "java focus" with a command line. <br>
</li>
<li>If gce() is not a polyline or is a polyline in another
figure (whose curve editor is off, or that has not the "java
focus"?), then the editor of the considered figure may stand
behaving has it presently does (i have no proposal to clarify
this).<br>
<br>
</li>
</ul>
<li>Setting gce() from the editor : <br>
</li>
<ul>
<li>if the editing mode is off and we select a curve (turning
grey) : no, gce() shall not be set to the selected (greyed)
curve. This would trigger major back-compatibility issues.</li>
<li>if the editing mode is on : <br>
</li>
<ul>
<li>if the interactive selection is done in gca() : yes,
synchronizing gce() to the currently edited curve would
answer to the issue. This synchronization would be more
intuitive than the current behavior that has 2 distinct
focus : Scilab's one (with gce()), and java one (with
interactions).</li>
<li>otherwise : no, because this would compel as well to set
gca() to the java focus. This would bring major BC issues.<br>
</li>
</ul>
</ul>
</ul>
<p>I don't know whether the editor is able to edit other types of
objects than polylines. If so, the proposed behavior could be
extended to them.<br>
</p>
<p>I hope that this analysis is clear enough (sorry for the length).
However, it may still miss important things... Any confirmation
would be welcome.<br>
</p>
<p>Regards<br>
Samuel<br>
<br>
</p>
<blockquote
cite="mid:1457950224.2472.39.camel@scilab-enterprises.com"
type="cite">
<pre wrap="">Le vendredi 11 mars 2016 à 23:42 +0100, Samuel Gougeon a écrit :
</pre>
<blockquote type="cite">
<pre wrap="">Hello Scilab Team,
Curve edition is a quite new feature: clicking on a curve allows to select it before either
interactively editing its points (move, delete, insert), or moving the whole curve.
But from outside,
is it possible to know which curve is currently/has been lastly interactively selected?
is there a way with a Scilab instruction to set the curve we want to edit data?
For moving it, ged(..) can be used: OK
For turning on data edition, the internal private useeditor(nFig,%t) can be used: OK
But how is it possible to set or identify the edited object, instead of priorly clicking on it?
I have checked that there is no relationship between the current object as returned
by gce() or set by set("hdl",handle) and the current object as clicked-on before data edition.
So, how to process?
Why not using set("hdl",handle) to preset the curve to edit, and using gce() to identify
the last curve edited?
Looking forward to read you,
Regards
Samuel
_______________________________________________
dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dev@lists.scilab.org">dev@lists.scilab.org</a>
<a class="moz-txt-link-freetext" href="http://lists.scilab.org/mailman/listinfo/dev">http://lists.scilab.org/mailman/listinfo/dev</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dev@lists.scilab.org">dev@lists.scilab.org</a>
<a class="moz-txt-link-freetext" href="http://lists.scilab.org/mailman/listinfo/dev">http://lists.scilab.org/mailman/listinfo/dev</a>
</pre>
</blockquote>
<br>
</body>
</html>