https://bugs.kde.org/show_bug.cgi?id=514739

--- Comment #6 from [email protected] ---
(In reply to Ritchie Frodomar from comment #4)
i'm sorry to hear that but i'm glad you at least have a friend who can help.

> I'd say the shortcuts breaking is its own bug entirely. 

yeah, sure, it's barely related to this bug, and is simply my own issues
specific to my setup. what matters though is that each zoom in and out is a
disk operation apparently, and its also not a behavior that user would not
expect, and it was not there in plasma 5. also it's an additional moving part
which may cause kwinrc file to be partially overwritten on power loss (i had
that issue a lot of times with plasmashell config bcz for it's own reasons it
literally updates every time i start and stop music player).

also saving zoom level between restarts as a backup in case your zoom shortcuts
stops working is not ideal. 

> It would be difficult for it to know whether to save the zoom level because 
> of a transition between effects or because we're about to log you out.

we wouln't have to know that, we save zoom level and state to disk on each zoom
in/out if "save to disk" is checked (like it is right now), and we do not save
anything to disk otherwise (like it was in plasma 5). 

but i mean, if you need that, and especially you are working on this effect
yourself, you sure know better. i would say that the majority of people would
probably not need zoom level to be saved and restored across logins, but they
probably would not care too much, and since it's now an accessibility feature
more than it is a desktop effect, i would agree with saving it to disk by
default.

i would still make a low prio feature request for "do not save zoom to disk"
checkbox though. i use meta + mouse wheel and it triggers several "zoom in"
actions per second (i scroll until i'm zoomed in exactly as much as i need to),
and generally avoiding extra disk usage to not spin up hdd unnecessarily or to
save some ssd health is probably a good practice too

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to