@VectorStyler Could we revisit this request? A visible indicator beside the active Settings preset would make it clear when the current settings differ from the saved preset file. For example, after loading a custom preset and changing a setting, its name could display an asterisk, such as “My Settings *”. Saving those changes back to the preset should clear the indicator. It could also be like VS working file that has been edited but not saved recently [image: 1790720868789-fd023bd8-1ad3-49c6-b7a8-ca6e774b7d05-cleanshot-2026-09-29-at-6.27.26-pm.png] This would remove the guesswork about whether later adjustments have been saved, especially before switching to another preset or restoring the defaults. If I switch presets while there are unsaved changes, an optional prompt could offer three choices: update the existing preset, save as a new preset, or discard the changes and continue switching. This would work much like the unsaved changes warning for a document.

@jpsimmons I tested these files. When opening, the font is replaced to Helvetica, here are the screenshots of the import as displays in VectorStyler. Send me the .vstyler file (by email) that results on your side when opening the PDF (and saving to .vstyler) [image: 1790661048242-importing1.png] [image: 1790661048294-importing2.png] .

Corel draw have such a feature But it doesnt have the awesome split Feature Here a Video how it works

@macos I could not replicate this here. Are you on Windows or MacOS?

@macos I tested with this font from Adobe, it seems that these are not supported by VectorStyler. I opened a bug on this and will try to add support for these.

@Boldline I opened a bug on this.

@VectorStyler Yes,That makes more sense. If identical parameters are required, fill in the same values in both fields and then lock the ratio for easier operation.

@Li-Xiao I will try to add these.

@Li-Xiao These are bugs, I will try to fix them

@VectorStyler Might as well make some improvements to Frame Text as well https://youtu.be/_URRsQ_dk34

@Boldline I added this to the features backlog, I will try to improve these smoothing operations in the future

@Boldline Added to the feature backlog, but maybe after 1.4

@Li-Xiao This seems to be a bug

@VectorStyler After experimenting a bit with the region option for color sampling, I have to say that it doesn't really convince me at the moment. The results simply aren't that predictable. I find using "Along Path" in conjunction with a clipping path to be more predictable— even if you might have to cut out the desired part later on. Here a pic [image: 1789376180210-clipped-along-path-small-part.png] . . . As for color sampling, as it is by now i find "Paragraphic" more useful and easier to work with. It would be great to see improvements in this area in future versions of Vectorstyler, as this method offers interesting possibilities for coloring vector object designs and serves as a nice way to create compelling color palettes.

Fixed in 1.3.026. Thanks

@Boldline I posted a request for something like this a while back. I looked for alternatives on macOS and found a few. While they aren't dedicated solutions, they offer quite extensive capabilities. The first one is Kando—a free app—and the second is Cirmenu, available on the App Store. There are quite a few apps of this type, but many rely on a subscription model, which isn't really my thing. Check them out; perhaps one of them will meet your expectations.

@Li-Xiao I will try to add this

@VectorStyler Just a test to see whether it can handle very large documents. Mine had 12K nodes, and the programme became slow and unstable. I discovered subsequently that switching from GPU to Software in the performance preferences helped, and especially turning on the options for, in my case, 24 threads. The biggest improvement then came from rendering layers as image, a setting that did not have an impact when the performance setting was set to GPU.

@Ink-Us please write an email to license at vectorstyler.com

@nocturnalYL I tested this, and it can be replicated. The issue here is that when rendering at low resolution, the image is positioned at sub-pixel positions and the margin can be clipped. In this case there is no other way than using higher resolution rendering.