I've just downloaded 1.2.072 and I see that the bug is fixed. Thank you !

@VectorStyler Thanks. It's a minor issue. this can be skipped.

@Boldline said in Changing stroke color with the option modifier enabled does not let me do so from objects on the artboard: Am I missing something to allow that? No, this is not supported. If not, could that be added? I will try to add this, have to check if there is an available modifier for this while picking color.

@Arde This could be caused by loading the last used printer options at startup. Try printing with an other printer and change the last used printer.

@VectorStyler Just to clarify, my issue was that I could not figure out what step I had forgotten to do at the end of the project. I had left the blend active in case I needed to make a change later. When I got the error while expanding the clipped live blend, it took me a while to realize my issue. So whether there is a warning that pops up that reminds the user they have live blends to attend to before it can act or it just expands it automatically for them - whatever is best for VS is what I prefer.

@VectorStyler Ok, thanks

@monsterfox It is not a bug, more like a naming issue. In VS there is a shape type that contains multiple paths. This is called the "Path Group" shape.

@EricP Yes, it can be replicated here. The Scale (maybe should be named Stretch) value is not supported by the Noise mode. I opened a bug on this to find a solution.

@VectorStyler let me know if you need me to send over anything or make another video to help narrow it down

@monsterfox I opened a bug on this.

@Fertuffo I opened a bug on this.

@monsterfox I opened a bug on these.

@monsterfox I opened a bug on this.

@monsterfox The problem is that other drawing apps do not support filled (or outlined) clipping groups. If these are not separate, then the stroke on the clipping group is also clipped (and it should not).

@Fertuffo Fixed!

@Subpath I opened a bug on this.

@VectorStyler Thank you.

@B-Vs-V Fixed

@VectorStyler I don't remember the exact name, but it's an option in the selection menu that's the opposite of "Select Parent." It's definitely not called "Child."

@monsterfox said in Strange error: I can replicate all these issues. Some are bugs, other are just the result of the reference trick in VS (but I will try to improve these also). Uniformly increasing or decreasing the size of graphics with the same dimensions can result in two different outcomes. This one is not a bug. The problem here is that the last two objects are references of other previously selected objects. Now if both the reference and its source is selected and we scale these, then the source is scaled (order does not matter), which makes the reference smaller, and then the reference is scaled again. So basically the reference was scaled twice (once its content and once the link). It is easy to replicate: draw a shape, Edit -> Reference, select both and scale. Not sure what would be a solution here (no one has the reference feature), but I will think of something. When converting the graphic to a path, the size shrinks, and it only returns to normal after converting it a second time. Again a result of the reference feature. When converting a "reference" (symbol) to curves, it will not convert it, but it will remove any transforms/shape effects on it, resulting in the smaller objects. Symbols (or references) should be expanded first with Style -> Expand Symbol. The solution here would be to automatically do an Expand Symbol when doing a convert to curves. When increasing the size of a graphic without selecting the stroke, the stroke may appear thicker. Here the problem is with the "too many options" of VS. Because we can have multiple strokes per object, each stroke can set if it is scaled or not when resizing (even if the object itself turned off the Transformed Stroke option). This Stroke level object can be accessed in the Appearance panel, by selecting the Stroke item and the Transformed Content in the panel menu. When simultaneously selecting a path and the underlying image to perform a node-disconnecting operation, issues may arise with the underlying image. This one is a bug, will be fixed. Graphics that are no longer in a grouped state can still undergo an unlimited number of ungrouping operations. This is also a bug, will be fixed.