Thanks to the success of the latest beta, I’m pleased to open this new discussion thread to invite you to test and explore the research of the OpenCutList Lab.
Opening our lab to the public is also a way we want to reward the community for their valuable feedback on the development of the extension.
What does this extension do?
OpenCutList extension generates cut lists, estimates, cutting diagrams, labels, exploded views, SVG, DXF for woodworking or similar projects.
For this first experiment, we suggest testing a part renaming module.
Using a selection and a formula written in Ruby, this module allows you to rename parts in cascade.
This module can rename thousands of component definitions in one single click
Here’s an example where the name of the parent group is used to change the name of the component definitions it contains. This can be useful for making two pieces of furniture unique based on the same initial geometry.
Get your test tubes ready, and thank you in advance for your feedback!
For the second experiment, we suggest testing the Deep Make Unique feature.
This feature allows you to “make unique” a portion of the hierarchy tree. So it is available on a Component Instance as on a Group
And it also works if you have nested components. Of course, within the portion, the instances are always linked to a common definition.
So, the component structure is not lost. It is simply “make unique” from the other instances of the model to allow modifications without fear of problems.
In reaction to this proposal we are pleased to invite you to test further use of math operation when entering length value in VCB in Draw and Handle Tools. The allowed operations are + - * /.
Examples :
2m+50cm/2
-2*(@+10)
This feature allows you to combine multiple units, parentheses, and the special character @ which refers to the length value given by the mouse location.
We’ve had several discussion in the past about improving the VCB.
In the latest I had suggested that anything in parenthesis be considered a math expression.
Whatever the protocol becomes, must still honor the current way that absolute and relative coordinates are entered. (I haven’t had a chance to view the code.)
Whatever the protocol becomes, must still honor the current way that absolute and relative coordinates are entered.
What do you mean by “relative” or “absolute” ?
This function only get a signed length from an expression. The use of this value as relative or absolute is delegated to the tool that uses this value, but the way the input could be catch doesn’t change, no?
SketchUp is magical! Even after 10 years of use, I’m still discovering new features! Thanks Dan.
Else, this feature is not incompatible with the read length logic proposed here.
<x, y, z> is a list of 3 lengths enclosed by <> used here as relative coordinates.
So, for exemple <1+2, 2m+50, 3*4> is possible in this logic. And as when reading a size, @ character represent the x, y, or z coordinate of the point under the mouse.
So the read sequence could be
detect <> or [ ] to determine if it’s a point
if yes, split on list separator
read 3 lengths
Else, reading a length or a point depends of the tool. Rectangle tool don’t need it for example.
.