Please don't maintain number of print copies between documents / print sessions

[fylraen]

In Publisher, I keep mistakenly printing dozens of pages because the number of copies to print is maintained across documents. I'll print 5 copies of a 1 page document, then go to print 1 copy of a 10 page document and print 50 pages by mistake.

Eventually I'll learn (sometimes I remember to check) but this seems like a very unforgiving setting. When I'm in a hurry I keep screwing up. I've probably wasted a hundred sheets at this point. It's a much smaller deal to hit print twice than it is to print tons of extra stuff by mistake. 

[Catshill]

And the failure to remember to print anything other spreads is equally annoying.

[Callum]

Hi Fylraen,

Welcome to the forums

This is a known issue logged to be fixed in a future update.

Thanks
C

[fylraen]

Thanks Callum, good to hear. Can't come too soon (for me anyway, hah).

[fde101]

12 hours ago, Callum said:

This is a known issue

Should this be moved to the bug report area?

[PaulEC]

it really baffles me the way Serif decides which settings should be sticky and which not!

[Bit Disappointed]

1 hour ago, PaulEC said:

it really baffles me the way Serif decides which settings should be sticky and which not!

It seems completely random, decided by different people with different roles.

[NotMyFault]

5 hours ago, Bit Arts said:

It seems completely random, decided by different people with different roles.

I agree to the first part before the comma, but assume that all such decisions made by a very small team of lead developers. And it more depends on a effort/benefit/risk evaluation.

setting sticky to file: must be store in metadata of file, or even metadata to individual layers. Print settings which tend to be OS dependent and could change dynamically even on same PC, so I understand this might be tricky.

settings sticky to App: needs to be added to one of the config files read by the app.

And then there is the constraint that Affinity hesitates to add anything new because once it is added to retail they can never remove such functionality to avoid being unable to open old files.

I really suffer from so many missing user/document specific settings, but forum uses are a bit quick to declare Serif staff lazy/dumb/ignorant directly or indirectly by micro-aggressive posts.

[Bit Disappointed]

These decisions shouldn't be made by lead developers. They should be made by people responsible for workflows and the entire user interface (one type of specialist) and implemented by other specialists. If lead developers are making these decisions, Serif is not working in a professional and up-to-date manner. Then they are decades behind on that particular point.

There may be architectural reasons why something desired cannot be implemented or must be done later.  But it's specialised professions and roles (!!!!) that ensure these things in product development. Software or not.

But, sorry, I've been a customer since 2007, I've seen these things overlooked, lost in updates, inconsistent and then fixed later via user feedback. And it can happen on iPadOS alone, where Serif needs a reminder before it's included there as well.

And very often it seems that it's not included because the idea hasn't been thought through, the workflow hasn't been thought through and tested. This has permeated my impression since 2007 based on my direct experience with the company, their development and updates and the products as such. And through comparison with other products and their development and user interface.

Ensuring these things in product development is essential from the start, as processes and roles become critical ingredients as you get further into the product's life, with complexity and dependencies steadily increasing. The user interface is often the first casualty.