Bug List for Version 1.3
-
@Subpath What I know is that macros can record the coordinate positions of operations, but the current actions don’t support this—they can only record the sequence of some regular operations. However, I think macros are basically useless in VectorStyler , because in the process of drawing graphics, you almost never encounter situations where you need to operate with the same coordinates. So the current actions should be more than sufficient.
-
Aside from that design may on a different position, there are definitely cases
where precise mouse positioning is useful. For example, with menus, which
are usually located in the same position.The actions in VS are sufficient in many cases, but unfortunately
too limiting for me, as they don't support some commands.
.
.
The macro recorder in CorelDraw was on a completely different level.
Because the recorded steps were are converted into Visual Basic
commands, allowing for to be edited after recording to insert loops or
additional commands.In one of my jobs, I frequently used the standalone tool "AutoIt," which also
allows for precise mouse positioning. The manufacturer's specific vector
graphics/printing program didn't have any actions or macros. "AutoIt" is a
well known Windows Tool for automating Tasks in App which didnt have
a Action/Makro recorder.With this, I was able to automate many tasks, such as creating numerous
DIN vector graphics symbols in various sizes. Doing this manually would
have taken weeks. (DIN is a german Norm, in this case for Symbols)
.
.
Unfortunately, VS doesn't follow Windows conventions sometimes in this
regard, so it is not possible to use AutoIt in it. I think that when scripting is
introduced (it's on the roadmap), the possibilities will expand in a way
where I would be happier with.
-
@VectorStyler

I've set the shortcut for copying an object's size to Alt+C and pasting the object's size to Alt+V. Draw any two shapes (A and B) of different sizes. When copying the size of A and pasting it to B, two errors occur:1. Error 1: After applying A's size to B, B retains its original size—meaning two instances of B are now generated (this is incorrect).
2. Error 2: Adding the "Copy Object Size" and "Paste Object Size" tools to the toolbar makes them unusable. I’m not sure if this conflicts with my existing shortcuts (preventing them from appearing simultaneously), but the shortcuts themselves also fail to work.It’s worth noting that using this feature directly through the menu works normally. I hope this issue can be resolved.
-
@monsterfox I opened a bug on this
-
@VectorStyler The issue with Error 7 remains unresolved
-
@monsterfox said in Bug List for Version 1.3:
When using the Path Offset effect, an error occurs when modifying the offset parameter in the Width Panel: for example, if you input 2mm, the actual offset is only 1mm. This error arises because the Width Tool and the Contour Path Tool adopt the same offset mode (offset on both sides).
I will try to replicate this.
-
Gradients no longer work. Updated to v1.3.004 64bit, Windows 10 Pro.

I just checked that only the 'Noise' type of gradient actually worked. Really odd… so most likely we got a bug.
-
@Evaelo Send me that file and Il will try to replicate it here.
In Settings -> Performance, try Software for the Compute engine.
-
@VectorStyler
As you command:
0_1766926041465_Gradient is broken.vstyler
-
@VectorStyler https://youtu.be/Ax06GN5JwRg?feature=shared0_1766927882644_合.vstyler
16.File Vulnerability Compilation & Fix Requests1. When multiple objects are selected and the Move Transform tool is used with the Transform Each option enabled, an error occurs: the sorting order of the graphics becomes chaotic instead of arranging from large to small.
2. Text input is unavailable within the file.
3. The Stroke Tool fails to work, and the corresponding stroke panel is also non-functional.
4. There are numerous broken paths in the file. If all graphics are selected and the Join Overlapping Nodes function is applied, some graphics will be duplicated in their original positions.
5. When two shapes are merged with overlapping areas, converting the merged shape to a rectangle will result in an unexpected positional offset of the generated rectangle.We sincerely hope these issues can be fixed in subsequent updates.