Hello all,
Indeed this would probably break some code. We should carefully check the
exist() usage within Scilab to ensure the output value is not passed to
macros/gateways checking for a “double” datatype. Code using exists() output
value as index or as condition might not be affected.
Don’t
Dear all,
I had already mentioned this a while ago
(http://mailinglists.scilab.org/Scilab-users-exists-yields-double-tt4039853.html),
but as I guess we are in the update season, it would be good opportunity
to fix this (if there isn't strong opposition, or a good reason for this
behavior, of
Hello Federico,
I agree with you that this would make more sense.
Could such a change be implemented for a point release?
I assume it would introduce some bugs in existing code relying on the
(unusual) double output...
Antoine
On 09/02/2021 03:24, Federico Miyara wrote:
Dear all,
I had
sorry
I am completely fine with xarrows instead of xpoly.
Philipp
Am Mo., 8. Feb. 2021 um 21:36 Uhr schrieb P M :
> Dear Users,
>
> I have a 3D-plot.
>
> Onto that, I would like to add a xpoly-line with the following specs:
>
> xpoly ( [0 1], [0 0], [-0.4 -0.4], 'lines' 0)
>
> in other
Dear Users,
I have a 3D-plot.
Onto that, I would like to add a xpoly-line with the following specs:
xpoly ( [0 1], [0 0], [-0.4 -0.4], 'lines' 0)
in other words: The polyline should be at the X-Y Plane, but shifted to Z =
-0.4
I know that I can just plot the line, but that would destroy the
