Wow! That is beautiful how the node is anchored not to go beyond the facing part of the arc.
If I understand correctly, although point A7 could not be created as an intersection node, it still gets created, just at ‘point of origin’… Could something be written to this effect in the error message? Something like “Point A7 is now located near point A” - just to let people know where to look for point A7.
My intuition tells me that it might be sufficiently handy to replace “Point intersect arc and axis” &“Point from arc and tangent” with a tool that would place a point along the arc a certain percentage of the way between the two edges. 0% & 100% would take over PfAaT, leaving all the other percentages for PIAaA. My judgement just tells me, “That’s not my case.”
Hi Grace… That could be done, although the origin (0, 0) isn’t always neccesarily near the draft piece basepoint A.
I think the main thing is the issue with a point erroneously flipping 180 deg will be fixed.
Edit: How’s this? Spruced up the warning text, added the footnote, and corrected the title bar to reflect what (tool) the warning was produced by, Also removed the superfluous “Seamly2D” in the title bar.
I don’t believe either of those tools needs to be replaced. The original intent of the intersect tool in Grace’s pattern makes sense, I just happened to find an odd case where it has odd behavior.
BTW, you can already use the point along curve tool to place a point somewhere between the 180 deg and 270 deg points… but you need to use the intersect tool first the create those points first. Again, the original issue of erratically being off by 180 deg is fixed.
Hi Anna… I’m guessing this is the most recent stable version of the program.
I’m not a Linux user myself, but you could try getting the latest weekly build on Github here: Click the “assets” link and the app image should be there.
I’ll try taking a look at the warning the program is throwing.
Also, the warning box is not consistent behavior. The first time I ran the Aug 3 Seamly.Appimage, it threw that warning. Note, I did not click “OK” to exit after it found no updates. Instead I clicked the x in the upper corner to close the window.
I tried to duplicate that behavior and this time I do not get the warning with either the x or the OK exit. I tried several times and in different order and it never failed again.
I tried to make that warning appear with the Sep 7 version and it did not fail. There are so many variables that I have no idea what else to try, but it is certainly not a big problem.
The fact that it did not find updates when I ran the Aug 3 version seems like a (minor) problem.
Interesting… I recently discovered that when building the program in debug mode in Creator, when closing any of the tool related dialogs with the window close X vs the OK button causes the program to crash. Hmmm.
At any rate Pneumarian is correct… something is wonky as the program should not be throwing a connection warning regardless, even if there are no new updates.
Update on the Arc/Curve Axis intersect tool… the changes are merged and should be in the next weekly build. Note that I had to add a fix to the fix to make it backwards compatible with (some) existing patterns without breaking them. It only applies when the axis point is inside an open curve, where I had to allow the intersection to flip on the axis, instead of constraining it like the initial fix did. If not then some patterns could break… or more specifically the “origin” point would be used. Not a problem if you know to just flip the angle 180 deg to fix the offending angle, but it would be a problem for existing cloud patterns.
Just going over all of this to see what’s done with this week’s upgrade…
And I really do like this idea of putting the tool icon next to the name of the tool. I think it will be a great help being able to see the icon at a glance when checking and changing formulas in a pattern… especially when helping people here on the forum. Languages change but the icon remains the same. Brilliant idea