Comment 8 for bug 1506256

On 15.10.2015 17:10, ~suv wrote:
> On 2015-10-15 15:51 (+0200), mray wrote:
>> @ How state gets saved?
>> I would be fine with any of the solutions.
>
> JFTR - I would not be fine with any of them:
> * Data loss is a no-go.
> * A modal warning dialog (with option to cancel) popping up each time the user clicks the toggle button would defeat its purpose as _quick_ toggle feature.
> * Littering SVG code all over with a new custom Inkscape attribute to store last used value of 'opacity' if 'opacity' was toggled off for a selected object is not really a solution IMvHO (it seems more of a workaround to mimic a visibility toggle (display on/off) per object via the object's 'opacity' style property (semantically wrong AFAIU)).
>

Your concerns all sound reasonable.
Please don't expect skills and experience - I'm not a developer.
My concern is just having an A/B test at hand.

>> The "Objects" offers what I need, but it isn't within reach (As "Fill
>> and Stroke" is)
>
> Please explain the unreachability of the 'Objects' dialog.
>
It is poor usability. Screen real estate is already a hassle. The
'Objects' dialog isn't something I ever use and something I would have
to *explicitly* pop up just to toggle an object on/off.

>> This defeats the point of having a *quick* A/B toggle.