https://bugs.kde.org/show_bug.cgi?id=438912
--- Comment #41 from Ahmed Faisal <[email protected]> --- (In reply to Joe S from comment #40) > (In reply to Nicolas Fella from comment #8) > > What exactly do you use/need from KMag? There's a native Zoom functionality > > in KWin (Systems Settings > Desktop Effects > Accessibility > Zoom) that > > works on Wayland > > The native zoom you refer to zooms EVERYTHING. > > KMag zoomed a focus area. > > I have two 27" monitors, so I very rarely ever need to run something full > screen and often I want to zoom a focus area while at the same time viewing > something in an unfocused area. > > Since the native zoom you refer to zooms everything it often moves the stuff > off the screen that I don't want zoomed. Why everyone INSISTS that full screen zooming is sufficient and satisfy the need for Projected zooming? Why nobody looks at Gnome and Cinnamon and see how they utilized the projected zoom by turning half of the screen (which translates to one of my two monitors) into a zoomed area display that displays beside/on top of/ your main working area! Why nobody studies history of M$ Windows 11 where the magnifier remained long months in its beginning when zooming focus actually NOT FOLLOWING the typing cursor and leave the task of following it to your mouse pointer just like gnome and Cinnamon are doing now? (another bug? I know. but it's so long lasting that everyone throws it on everyone else, and GUI developers accusing the browser developers of not coop. however, they did with Windows magnifier app only a couple of years ago!) -- You are receiving this mail because: You are watching all bug changes.
