Variable Table

[DeadlyDad]

One of the most inexplicably absent features of SolveSpace is the lack of a variable table, where users can define variables & arrays that will then be used to help define constraints. This becomes exponentially more important when you are developing a new product where you aren't completely sure what will be needed and require a way to quickly make even major changes without chasing constraints. ("Hey, Bob. We redid the math and M8 bolts for the main support structure won't be nearly strong enough. Change them all to M12s." ...and there are 1,260 of them. ...and there are 800 other M8 bolts connecting things to the main support structure that need to stay the same size. :shudder: So much for Bob enjoying his Saturday at home!)

With a variable table available, however, if someone wasn't too sure which metric bolt size they might end up using to mount a plate, they could create an array called 'BoltM' containing the various dimensions for the different sizes. To constrain a hole for an M8 bolt to easily slide through, they might enter BoltM[8][ShaftDia] + BoltM[8][ShaftTolerance]. If you came across that formula in a constraint--even if someone else had created it--you would instantly know its purpose. In fact, that example is a poor one because the '8' is hardcoded and changing any holes using it would require chasing down all of the constraints that use it. Far better would be to use 'MSSBoltSize' (or w/e) in its place, so by changing that variable, you can instantly change the size of all of the relevant holes that use it. In poor Bob's case, changing all 1,260 references--there would, in reality be at least twice that number of constraints--becomes a five-second job and he would get to chill for the whole weekend. Hooray for Bob!

[DeadlyDad]

It just occurred to me that Blender would also have a list of variables that might be able to be referenced, though I'm not sure how helpful that would be as I'm decidedly NOT a Blender guru.