Hey,

this is kind of a follow up to this discussion:
http://www.polargraph.co.uk/forum/polargraphs-group2/troubleshooting-forum5/saw-tooth-circle-and-dubious-text-thread395/

But as it is slightly different, I thought I start a new topic now:

After some experimenting with other drawing styles I got back to my pixelation "problem"....and tadaaa: new surprises! 🙂
I know that you changed something in the preview settings, as it runs MUCH faster now (thanks!) 🙂 ....but it seems to have influence on how SVGs actually get drawn...

I took the exact same SVG I generated through Illustrator (one with rectangles (upper) and the other one with circles (lower)) and generated the code once for each in 2.1.1 and 2.3.0.
I didn't screenshot the vector path preview..but already the preview of the file looks very different in both versions...and it gets exactly drawn like in the preview of 2.3.0 (also loading of the same vector file in 2.3.0 takes much longer....so I guess you some pre-processing?)

Somehow the circles-version looks very circular now when actually drawn from version 2.1.1 (no jittery saw-tooth circle problem, weird...) and in version 2.3.0 they are little hexagons...in the preview AND actually drawn out....(love the result though! 😀 )

In both polargraphcontroller versions I changed the setting to RS.UNIFORMLENGTH and both run the 1600 revs settings....

So my question:
Can I actually change it "easily" and temporarily back somewhere in the settings or the code, that circles get processed with more control points and not just 6? I mean I don't really mind as I can still use the 2.1.1. but at one point you might be so far off in the future that it won't work anymore, so I would like to be prepared 😎

And many thanks Sandy for your continuous great efforts and work on the Polargraph! So much appreciated!

I run the app from source directly through Processing (2.2.1, haven't upgraded yet -> kind of a "never touch a running system" approach 😉 ) (the executable doesn't run on my computer...haven't figured out why...I guess it's the XP -> the other "never touch a running system 😉 , but it doesn't matter, as I know my way around processing enough to do so)

I am pretty sure I still use the geomerative library that came with the polargraphcontroller bundle on November 10th last year. But checking online, it seems the library hasn't changed since 2012 anyway....-> http://www.ricardmarxer.com/geomerative/ ?

Well, I changed the polygonizer back to RG.ADAPTATIVE and that seems to bring back our proper rendering.

  
  RG.setPolygonizer(RG.UNIFORMLENGTH);
//  RG.setPolygonizer(RG.ADAPTATIVE);

https://github.com/euphy/polargraphcontroller/blob/master/polargraphcontroller.pde#L543

Don't know why I didn't spot that in the diff as the likely culprit earlier.

So I remember the discussion that preceded this change, and the change was targetting at improving rendering in a slightly different context and scale. Personally, I think angular accuracy (as shown in DaniK's small-scale work) is more noticeably problematic than the curvey accuracy that is discussed in the "sawtooth and dubious text" thread (http://www.polargraph.co.uk/forum/polargraphs-group2/troubleshooting-forum5/saw-tooth-circle-and-dubious-text-thread395/), so I'm going to switch back to RG.ADAPTATIVE as the default for the next release.

Thank you very much to DaniK for providing such excellent troubleshooting support around this - really appreciate that.

I'll try to get that setting as a configurable thing, stored in the properties file, because I can see reasons for changing the setting to suit the artwork.

DaniK, can you try changing that line to ADAPTATIVE too, and see if it fixes it for you too? I kind of had the impression that you'd already tried it.

sn

Sandy this is awesome!!! Thanks!

I didn't even realize how terrible zooming was before I knew how easy it could be 😀 (I have to admit, that might be the best update so far, because I didn't expect it..ha!)

The new polygonizer feature is amazing! I love it!

But just fyi, I tried both options then (RG.ADAPTATIVE and RG.UNIFORMLENGTH) in the polargraphcontroller 2.3.0...and just now again to verify...it doesn't change anything in the vector-preview just the queue -preview....but it is anyway now irrelevant... 😉 In 2.4.0 it works like a charm.

I love the fact, that i can control that output now, that came out accidently here...I am going to fake wind-vector-simulations (CFD) now with my polargraph 😎

A BIG THANK YOU AGAIN!
D