Queries Regarding VectorStyler 1.3
-
@Boldline very well said
-
@Boldline Thanks for your perspective. I just want to note that it took 4 years to move from version 1.1 to 1.3, and the updates have been as amazing as expected. However, if the updates continue at this pace, it will take 20 years to reach version 2.0—by then, many of us will have already ended our professional careers, which is really regrettable. That’s why I’ve been feeling a bit anxious, and I might have expressed my emotions inappropriately. I apologize to everyone for that.
-
Where i miss the relation a bit.
We're talking about a program that costs $95, not one
with a monthly subscription fee.All previous bug fixes and improvements until now have been free.
Without wanting to do anyone wrong, I see no real reason to
complain about the length of the development process.
-
@monsterfox Thank you for expressing your concerns. I get it. Nobody wants to wait twenty years for progress. I confess I still hope we see a companion pixel editor and desktop publishing tool that works alongside VS well before the 20 year mark! Some of the groundwork already in VS might even speed that up. Either way, I am glad VS exists and that it delivers a stronger and more powerful vector editing experience than what I started with years ago.
I do not have inside info, but based on how fast bugs were fixed and roadmap features were shipped, it feels possible we may not see long strings of versions like 1.7 or 1.8. By the time we hit 1.5 or 1.6, the core features might be finished and the next logical move could be 2.0. At some point everyone needs to decide when VS feels complete enough for full professional use. For me, most of what I need is already in place or can be handled through outside tools. I get almost all my daily work done in 1.3, which is a massive leap from the 2020 beta where I started.
That said, I still have a list of needs and nice to haves that would make the app even stronger. I am sure you do too. Hopefully the current feature set already covers most of what you rely on. Keeping some perspective, VS is already well ahead of Affinity and plenty of people use Affinity as their main tool!
I cannot guess how difficult or time consuming the remaining roadmap tasks are, but I hope the updates continue with the same momentum. Without pushing the developer into commitments he does not want to make, and while still leaving room for surprises and his willingness to respond to user requests, it might be worth having more focused conversations soon about which tools and features we see as the top priorities for 1.4. That way @VectorStyler can make his final decisions knowing where we as the community are coming from. As @Subpath mentioned, we've been given so much value already in VS and less has been expected from us. I don't want to look a gift horse in the mouth! I know we're all so grateful to @VectorStyler for his contributions to our vector design careers.
-
@VectorStyler Will a halftone effect with dot merging be added to the halftone panel in the future?
-
@monsterfox said in Queries Regarding VectorStyler 1.3:
@VectorStyler Will a halftone effect with dot merging be added to the halftone panel in the future?
In the case of the first image of this thread:
The problem is not with dot merging, but with the shape of the halftone. Those halftones (first image) are created in postscript as images. So this exact case will not be added to the halftone panel.The second image from this thread might be possible, I have this in the backlog and will try to add it as soon as possible.
-
@VectorStyler After upgrading to version 1.3, the program's running speed has been significantly improved compared to version 1.2, but occasional lag issues still occur. This file is a typical example—the extremely large number of nodes in the graphic causes lag when moving objects. I have tested the object-moving function in several programs: Adobe Illustrator runs without any lag; older versions of CorelDRAW have slight lag, while the newer versions suffer from noticeable lag. My primary program at present is FreeHand 9. Despite being released over two decades ago, it still ranks among the most smooth-performing software and shows no lag at all when moving this object. Finally, I tested Inkscape, which has a reputation for lagging. I expected it to be extremely sluggish, but surprisingly, its object-moving speed is even faster than that of VectorStyler.
Therefore, I’m curious about why such lag persists despite the upgrades to both my hardware and software. Could it be that VectorStyler’s lag is attributed to its display enhancement features, while FreeHand 9, which lacks such features, runs faster?
0_1766243159919_卡.zip
-
@monsterfox I will add this to the backlog, but not sure if performance can be improved much.
The time is spent on rendering those outlines.
-
@VectorStyler Is it possible to add a view mode similar to FreeHand’s—one that removes image quality enhancements and prioritizes speed? The existing pixel mode also lags, and sometimes it’s even more laggy than the normal view mode.
-
@monsterfox said in Queries Regarding VectorStyler 1.3:
@VectorStyler Is it possible to add a view mode similar to FreeHand’s—one that removes image quality enhancements and prioritizes speed? The existing pixel mode also lags, and sometimes it’s even more laggy than the normal view mode.
I will think of something before the 1.4 release.
