Ok so the “Variable not found” error seemed to be triggered by the fact that the equation atoms weren’t properly waiting for all their variable parent inputs to be ready. I pushed a fix, let me see if you see this specific issue come up again.
2 Likes
Ok, I’ll try making and using root variables
So I don’t know if this is the same issue but it sometimes erases inputs in shapes and things. In this picture the rectangle originally had variables in both inputs. Now only y is erased. I don’t remember what it was.
1 Like
I see. I have not seen this happen but I will keep an eye on it. Does it happen to you after reload? Or do you have any sense of when it might be happening?
2 Likes
After reload. Everything works in a single session. I think if it can’t find a value on reload sometimes it just deletes the entry.
Feature thought.
Would it be ok for extract tag atoms to display the name of the tag that has been extracted once one has been selected as text on or near the atom icon or as it’s title like the equations do?
Also minor bug. The Gcode atoms seem to be delicate? When I change things they all go red until things are refreshed or another variable is changed.
https://abundance.maslowcnc.com/wouldchuckit/Hollander_Beater_Attempt_Export_and_Assembly
1 Like
Thanks for pointing this out. I think the shared parameters are causing the gcode operations to cancel each other out (Bug). Will work on getting it fixed! Also the extract tag display name seems like a good idea, i’ll add that too 
Thanks for all the feedback
Also, excited to see the hollander come together! I built one from scratch a few years back but Abundance wasn’t nearly as functional back then to try to design it in here
2 Likes
Ha. That’s fun. Very few people have built one. If you see any tips for my design please suggest them. I will keep you posted with real world progress when I get there. It will be a while. Planning to cut it out of HDPE