https://bugs.documentfoundation.org/show_bug.cgi?id=139164

--- Comment #28 from Telesto <[email protected]> ---
(In reply to Eyal Rozenberg from comment #27)
> You really can't tell how much demand there is for a change by counting the
> CC list size. There is some correlation, of course, but CC list membership
> or dupe count are meaningful signals only for distinguishing between
> _massive_ demand and almost-no demand. Not to mention how some people just
> adapt or "live with it" even though they would have preferred things to be
> different.

I'm aware of the issue :-). I'm mostly at the other side of the argument,
wanting a UX change, but lacking proof of demand. 

> > Instead of keeping thinking how the preserve the feature in advance. Which
> > evidently comes at a cost (like cluttering the UI) without clarity about
> > user demand...
> 
> That's also a possibility. But then - would you really be against allowing
> export/print of a selection from its context menu? That's one of the options.

I'm not necessary against.. my 2 cents. However I do ask myself, where are the
boundary's. There are so many users with so many different desires. It becomes
a slippery slope if add a specialized function/menu entry for each and every
case diverting from baseline. Each and every request has its merits and makes
often sense in the isolated case(aka "corner-case") 

Another uno command, another entry in the customization dialog :-). Another
function that has to be maintained, documented, translated. Something else that
can cause bugs. And what should happen if you use a function without anything
selected, only a blinking cursor. Should print an empty page? Automatically
switching to 'print/ export to selection' feels like "feature creep".

I already struggling with 'Export Directly to PDF' because I never know which
settings are used. For example: does it "print a selection" or "full page".
Personally I prefer to 2 step process. Export as PDF, knowing what it does (or
supposed to do accordingly to dialog, probably not always the case)

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to