@Arde Not possible to have limited steps. Object blends can be used for fixed step color transitions. Would such a feature be useful otherwise? EDIT: it is not difficult to add such a feature.

@vectoradmin By the way, loving the control I have with the shapes panel. VS gives me so much freedom and control

@vectoradmin thanks I overlooked it. i got it

@Boldline I added a path brush tool improvement task to the backlog.

@Petar_MK @Kyriakos Doesn't VS already have some bitmap halftone kind of function built in already? I agree with @vectoradmin that it's probably important to not stray too far from keeping the application a vector-based focus. That said, the ability to do a few things in raster is helpful - I need to play with it more, but the halftone bitmap abilities already inside VS are awesome

@861475_VctSt Yes, that will work fine.

Thank you.

@encart This is a known open issue. The problem occurs at the cleanup phase after offsetting. There are a number of stroke and offset bugs related to this. It will be fixed, but it is a challenging issue

@Gremriel This looks like a bug.

@vectoradmin Ah, that's nice. I''ll patiently wait for that.

@b77 Thanks for your help and patience! I wasn't even thinking about the panels possibility for location of that. Got is set th way I want now.

@fde101 said in Use the word Hairline rather than 0.0 pt in Stroke display field: In the digital world, a "true" hairline is defined as the smallest width line capable of being produced on a given output device, this being exactly 1 pixel wide for the most part. It is not a fixed literal width but rather something that changes depending on what the image is being displayed or printed on, thus why various applications display it as "Hairline" - there is not an actual width to be displayed numerically. @fde101 Yep, you nailed it. It's the industry standard nomenclature, that's why I prefer/suggest it be used in VectorStyler.

@encart Try using Snap To Points when drawing, this will align the points of the rectangles to the triangle corners. Also: shape builder has this known issue of not always handling well sides that are exactly touching. A little bit of overlap helps there,

@vectoradmin I don't think these should be visible when the shape is procedural(?) or the text is still editable. Once it's been converted to curves, yes, absolutely. But not when it's in its special editable form, I would say. Enabling this setting by default would be great if the above conditions would be met — it would serve as a subtle hint that the shape or text is converted to curves.

@861475_VctSt The above post is It should have been uploaded to "CJK, Japanese observation (1.0.024 ~)". Next time, I will create a new topic. Please read as it is.

@b77 I agree with your solution. It is the most intuitive and simple. I proposed an additional key because I do not know how big a problem the redesign of this mechanism will be. Especially considering the amount of bindings that are under the hood.

@encart If I understand correctly, tracking works, but kerning does not? What is the font name used? kerning (Metric mode) requires that the font defines the kerning pair tables.

Character tool is great for modifying single characters - then you keep all text properties. Using Break apart, I would intuitively expect to get single curves that I could modify like shapes. Immediately after use, quickly and smoothly. Basically, the only difference with the current behavior is that you get split into separate paths right away. No need to use Break apart twice. As like as it is with objects created from a few paths. https://recordit.co/ney48Ij2hX

@encart There are still places where performance can be improved. In this case, a still open issue is that path offsetting with large offsets can result in artifacts. To explain what is going on in this picture: a complex shape with multiple parts has a somewhat large stroke offset set to the outside. This means that at each redraw this offset is computed, cleaned up (which is not working well at large offset) and united with the various parts (each path from the text). This all happens on the CPU (compute engine will not help here, that is used for image effects). The only way to work around this for now is to have separate objects for each of those glyphs, if they are converted to curves. And maybe avoid using very large outer/inner offsets (centered stroke is somewhat faster). Also if there are complex shapes, sometimes it is better to expand the stroke, or use the Outline Path , or Offset Path shape effects, where all that offsetting / union is cached for rendering. But these will not get rid of the large offset artifacts.

@Boldline The refresh issues are fixed in the new build, but the empty rectangle will remain for now. This support shape is needed even after the brush expansion, because it defines the area of the vectors (from the brush) that are stretched along the path with the bend effect (the result of a brush expansion).