@VectorStyler two bugs has been fixed. Thank you.

Thanks, uninstalling everything and re-installing fixed it.

@Ayo it might be that the draw inside icon was not exported correctly. I will check this later.

@Ayo said in Restored node size in settings: Still can not set 'Transform Selection Node' node size to small (or large) rectangle. Remains medium. This is probably a different bug, I will try to find out what causes this.

@VectorStyler said in update 1.2.005: VectorStyler 1.2.005 release notes Added a preview button to the create guidelines view. @VectorStyler & with "All artboards on canvas" Very helpful, thanks ... and of course for all great improvements

@VectorStyler This is what I am experiencing. Column and inset options work when text in the frame are selected not the frame. https://recordit.co/0haxza4pA5

@Ayo Replicated here also. For now the hovering will work for shapes that are converted to curves already. I will try to improve this.

@Ayo said in Can't find the Object Selection Frame: Only if I increase the line thickness extremely to, say, 8 point, then I see it. I will look into this.

@Ayo said in Hyphenation doesn't seem to work: That leaves me with three unanswered questions. Yes, sorry about the late answer, was focusing on replicating the bug The default hyphenation is either no hyphenation, or whatever hyphenation was defined at "parent" level (hierarchy of style sheets). About the character options repeated in paragraph. Yes, actually all character options can be defined at paragraph level as the default character settings for that paragraph, and then local character overrides are defined for a part. This is the same in other drawing and typography apps. The settings in the character options override (if set) the paragraph settings.

@Ayo It is a bug. Seems to work with keyboard selection. Will be fixed for the next build.

@Ayo said in Character Panel additional options appearance: Improvement proposal for appearance Character Panel additional options Thanks for the suggestions, these look much better. I will try to add them ASAP.

@Ayo Can be replicated here also. I opened a bug on this one.

@Kumr Could be related. I will improve this.

@Ayo Could be that is is missing in 1.2. I added this to the backlog.

@Ayo Besides what @Boldline mentioned, I just wanted to say how it makes me happy to see influx of new (serious) testers that run VS through its moves and add to the conversation what can be done better / different / would improve their workflows. I too am testing VS on and off over a couple of years now and can see the large amount of improvements that have been realized in this time. And not just improvements, also extra functionality (such as support for Japanese typography) and things that we cannot do easily in other programs. Contributions like yours are invaluable and help to shape VS into an outstanding application.

@VectorStyler Maybe I overstep my role, but I was still thinking about this (mentioned it also in the mis-leading pdf) and thought that the cause might lie in the use of the font metrics font size 'Height' that includes the fonts internally specified leading specified by the font designer. Advanced DTP programs can control the line spacing in terms of point size and use body height (sum acender + decender), but word processors default to single line-spacing are using the build-in line-spacing specified by the font designer. It is important NOT to use the so-called 'default build-in line-height' wich is basically a font designer's personal preference which is irrelevant and undesirable in a professional environment. Leading is highly dependent on line width and use/medium. Maybe I am wrong, I am not a developer. "Maybe I heard the clock chime, but do not know where the clapper is" (dutch proverb) I'm just worried.

@Ayo said in Unit Soup: When I specify units for Type as points I want to see points (supervisory). Found the bug. The various leading, etc fields use the wrong defaults. Will be fixed.

@Ayo said in Artboard stress: Stack order in panel represents print/export order. That's correct, isn't it? Yes, stack order in Canvas& Artboards panel.

@encart Clearly a bug, added it to the backlog.

@VectorStyler OK, could be that the mockup is oversimplifying things — this background color needs to be added as content that can accept transparency masks, effects, etc, right?