Jump to content

Recommended Posts

 

As you can see, there are many alternatives to the Autotrace function, i.e. its priority compared to much more important functions (for example vector warp) is understandably lower.

Affinity Store: Affinity Suite (ADe, APh, APu) 1.10.5.1342, 2.0.4.
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 22H2, Build 22621.1702.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 22H2, Build 22621.1702.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

Quote

As you can see, there are many alternatives to the Autotrace function, i.e. its priority compared to much more important functions (for example vector warp) is understandably lower.

Even more reason to have tracing in Designer. Every (vector) application I know of has this feature, it's a core function.

It's also not that hard to make, so I see no excuses for not adding it.

Link to comment
Share on other sites

1 hour ago, Ole-André said:

Even more reason to have tracing in Designer. Every (vector) application I know of has this feature, it's a core function.

It's also not that hard to make, so I see no excuses for not adding it.

Seriously, tracing an image (turning a raster image into vectors) is a one-time procedure to be done to an image during the design process. The result will be used in further workflow and in a design/layout. It's not that much of a downside, using dedicated apps for this process. Neither in time needed for this, nor in functionality. 

For me, a design software should provide the steps, which I repeatedly have to do or edit during the workflow of designing/layout. Tracing clearly isn't one of the "constantly repeating steps" one usually needs during a project.

»A designer's job is to improve the general quality of life. In fact, it's the only reason for our existence.«
Paul Rand (1914-1996)

Link to comment
Share on other sites

Bearing in mind that there are pretty decent free or inexpensive third party options out there, I think it is a waste of time to code it into Designer. In fact, I don't rely on one single tracer, having two already installed plus an online one, as they provide different results. So, for me, having one more tracer built into Designer should be nice, but absolutely not important.

Link to comment
Share on other sites

2 hours ago, Valentín Benavente said:

Bearing in mind that there are pretty decent free or inexpensive third party options out there, I think it is a waste of time to code it into Designer. In fact, I don't rely on one single tracer, having two already installed plus an online one, as they provide different results. So, for me, having one more tracer built into Designer should be nice, but absolutely not important.

Well, by that reasoning developing Designer is a waste of time since free alternatives exists (Inkscape).

4 hours ago, Andy05 said:

Seriously, tracing an image (turning a raster image into vectors) is a one-time procedure to be done to an image during the design process. The result will be used in further workflow and in a design/layout. It's not that much of a downside, using dedicated apps for this process. Neither in time needed for this, nor in functionality. 

 

And doing that in Designer is the correct workflow, if I need to use third-party applications Designer has failed.

 

It a simple feature request, not hard to implement IMHO.

Link to comment
Share on other sites

37 minutes ago, NNN said:

Do you think you can learn in an hour or two to play any instrument only by listening to professional musicians how easy they play?

I think that the very fact that there are so many different implementations of the autotrace functionality that provide different and often completely unsatisfactory results, and that there are specialized companies that have made a very good business out of it, clearly points to the fact - that it really not easy to implement. Otherwise, everyone would write the ten lines of code themselves, and not have to turn to a professional solution.

Affinity Store: Affinity Suite (ADe, APh, APu) 1.10.5.1342, 2.0.4.
Dell OptiPlex 7060, i5-8500 3.00 GHz, 16 GB, Intel UHD Graphics 630, Dell P2417H 1920 x 1080, Windows 11 Pro, Version 22H2, Build 22621.1702.
Dell Latitude E5570, i5-6440HQ 2.60 GHz, 8 GB, Intel HD Graphics 530, 1920 x 1080, Windows 11 Pro, Version 22H2, Build 22621.1702.
Intel NUC5PGYH, Pentium N3700 2.40 GHz, 8 GB, Intel HD Graphics, EIZO EV2456 1920 x 1200, Windows 10 Pro, Version 21H1, Build 19043.2130.

Link to comment
Share on other sites

3 hours ago, Ole-André said:

And doing that in Designer is the correct workflow, if I need to use third-party applications Designer has failed.

Utter nonsense. Using dedicated tools for single special tasks is the correct approach. Not recognising this is failing. I wouldn't want Designer doing 3D renders either, although I need them in quite some of my clients' work.

As @Pšenda already stated—and I agree with the "often completely unsatisfactory" part, which is true for most implemented auto tracing features in other design apps:

2 hours ago, Pšenda said:

I think that the very fact that there are so many different implementations of the autotrace functionality that provide different and often completely unsatisfactory results, and that there are specialized companies that have made a very good business out of it, clearly points to the fact - that it really not easy to implement. Otherwise, everyone would write the ten lines of code themselves, and not have to turn to a professional solution.

Dedicated apps for such tasks, which solely concentrate on creating a useful output, are there for a reason. It's by far not "an easy thing" to implement, otherwise Corel's or  Adobe's built-in vectorisation probably wouldn't fail that often.

»A designer's job is to improve the general quality of life. In fact, it's the only reason for our existence.«
Paul Rand (1914-1996)

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.