ArcTo in shape script (and other quirks)

[qwerty]

Can someone confirm that the following shape produces non-sense:

Code: [Select]

shape main {
      MoveTo(50,50);
      ArcTo(0,0,100,100,100,50,0,0);
}
Even worse:

Code: [Select]

shape main {
      MoveTo(50,50);
      ArcTo(0,0,100,100,100,50,100,0);
}
q.

[EXploringEA]

Hi Thomas

All depends on what you mean by nonsense - they produce incomplete ellipse like shapes.  I could post picture if only I knew how on this forum.

BR

[qwerty]

The 2nd looks like this:

(Just use the img tag above and insert the public dropbox link)

This does not look like what is described in the help (partial arc).

q.

[EXploringEA]

Mine look similar but not the same - so even more interesting.  

[qwerty]

Obviously it's wrong then. Thanks for the feedback :-)

Sparxians: you may open a ticket if you feel that this needs correction. I will definitely NOT send a bug report (as you may know I'm sick of that).

q.

[qwerty]

Here's another one:

vs.

SetPenWidth seems to be "pre-evaluated" in the script.

q.

[qwerty]

And one or two more:

SetDefaultColors will draw everything invisible.


SetFillColor does not do anything. Instead all elements are painted in the user defined color.

Well, I'm just at simple examples. What surprise will there be hidden in more complex things?

q.

[qwerty]

PrintIfDefined doesn't print anything at all. Neither truepart nor falsepart. Further the help says falsepart is optional. The compiler however claims that 3 parameters are needed. Anyhow: why does that method exist if there are control structures??

q.

[Eve]

I just noticed we have a fix pending for arcto in the preview window. That could be the cause of that issue.

[qwerty]

Thanks or the info. Maybe you could have a look at the other ones too.

q.