<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Stanislav,<br>
<br>
Le 31/03/2013 11:12, Станислав a écrit :<br>
</div>
<blockquote cite="mid:5157FDE6.3060003@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">30.03.2013 08:14, Samuel Gougeon
пишет:<br>
</div>
<blockquote cite="mid:51564A8D.7010606@free.fr" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
This vectoriation is a good idea! I agree that implementing it
in the same function<br>
as for only one polygon is much preferable, w.r.t. coding a
specific xrpoly<b>s</b>()<br>
function as it has been done for most of other functions
plotting geometrical <br>
shapes : xrect > xrects, etc..<br>
<br>
</blockquote>
I didn't know about such division and I don't understand why it
has been done. If I want to plot n rectangles what function
should I use? xrects? Even if n = 1?<br>
</blockquote>
yes, if you want to fill it with a color :
<a class="moz-txt-link-freetext" href="http://help.scilab.org/docs/5.4.0/en_US/xrects.html">http://help.scilab.org/docs/5.4.0/en_US/xrects.html</a><br>
There is neither logic nor sense for the user, but with xrect()<br>
you won't be able to fill it with a color as parameter. <br>
So you should assume and use that nb>=1 allows nb=1 :-)<br>
<blockquote cite="mid:5157FDE6.3060003@gmail.com" type="cite">
<blockquote cite="mid:51564A8D.7010606@free.fr" type="cite"> Since
a SEP is running, here are some ideas of other possible
developments<br>
for new features:<br>
- why not <b>vectorizing also n, r and theta</b>? (with default
= scalar)<br>
</blockquote>
It is a good idea and it is very simple to implement.<br>
<blockquote cite="mid:51564A8D.7010606@free.fr" type="cite"> - <b>filling
= filling_color</b> (optional): to fill the polygon(s) with
respective <br>
colors (vector of indices in the color_map). <br>
a color<0 means that the line (border) must not be
plotted.<br>
- <b>symbol=[symbol_numbers, symbol_sizes]</b>: to put a symbol
on the angles <br>
(the same on all angles, but may be different from a polygon
to another one <br>
=> vectorized = mx2 matrix).<br>
- <b>isoview=%t</b> option, to force the targetted axes to be
isometric to show <br>
a truly regular polygonal (see the present mis-shaped sample
in help xrpoly)<br>
</blockquote>
I am not sure that it is a good idea. This function use the axes
scale and I am not sure that user want to have isometric axes.
</blockquote>
If a user wants to plots a regular polygon, don't you think that one
prefer to<br>
see it as regular ? Backward compatibility would be insured by
keeping the <br>
default isoview=%f. But i would easily bet that in existing codes,
xrpoly(...)<br>
commands and 90% of the time preceded or followed by something like<br>
ax = gca(); ax.isoview = "on";<br>
and that for 9% of the remaining 10%, it would not injure to add
isoview.<br>
<br>
<blockquote cite="mid:5157FDE6.3060003@gmail.com" type="cite">
Besides, backward compatibility can be damaged. But it can be done
in separate function. And in one year somebody will ask: "I am
newbie and I didn't know about such division and I don't
understand why it has been done." <span class="moz-smiley-s1"><span>
:-) </span></span><br>
</blockquote>
So, finally you understand why there are xrects() after xrect(), and
xfrect()<br>
(yes, enabling filling deserve a totally new function, don't you
think? :-(( ),<br>
xarcs() after xarc(), xfarc() after xarc(), and obviously xfarcs()
(no, it is not a joke. <br>
just check)...<br>
<blockquote cite="mid:5157FDE6.3060003@gmail.com" type="cite">
<blockquote cite="mid:51564A8D.7010606@free.fr" type="cite"> - <b>showAll=%t</b>
option: => enlarge axes bounds up to the external bounds of <br>
generated polygons<br>
- returning the <b>vector of created handles</b><br>
</blockquote>
I don't understand what "returning the <b>vector of created
handles</b>" is for?<br>
</blockquote>
to easily enable any further tuning for other attributes of the
lines (color, <br>
thickness), the filling color of markers, etc.<br>
For instance, stars of the example could be made yellow. This would
give :<br>
<br>
<tt>H = xrpoly([0.5 0.5], 12, 0.4, symbol=[14, 8],
filling=-color("cyan"), isoview=%t)</tt><tt><br>
</tt><tt>H.mark_background = color("yelow");</tt><tt> // and for all
polygons in a once<br>
</tt><br>
<img src="cid:part1.08030103.03050403@free.fr" alt=""><br>
<br>
</body>
</html>