Version: (using KDE KDE 3.4.1) Installed from: Unlisted Binary Package On Linuxtag 2005 a people told me that KMag is only usefull for graphics artists to check a pixel image and not for eye-disabled people because KMag is a window that hides a rectangle area on the screen. An eye-disabled person cannot move the window around to see what's beneath it. KMag needs to be in an area where no window can be beneath it, for example in a bar at the top or any other screen edge. This can easily implemented in making KMag a kicker applet.
I agree. or it might be nice to add a mode in which kmag magnifies what is beneath it (obviously the centre of what is beneath it). or let's have an option ich which kmag magnifies everything as before but simply treats the screen as if the kmag window wasn't there at all - that it's invisible to kmag. would this be possible? it would seem like the most sensible thing to do anyway. who wants to magnify the contents of the kmag window when you could just as well increase the magnification? as an example example: setting kmag to fullscreen-magnification-mode and then maximising the kmag window yields some bizarre results at the moment as every new refresh adds another kmag window into view.
i would vote for a magnification mode where the kmag window "moves" with the mouse cursor so that everything on the screen can be magnified and accessed...
I would vote for a bar at the top of the screen, similar to the kicker bar but thicker (if possible with a adjustable width). I guess a kicker applet fills an entire toolbar at the top is also OK. All windows are resized to accomodate the bar and instead of the kicker view, it (or the applet) shows a magnified version of the screen.
*** Bug 320755 has been marked as a duplicate of this bug. ***
*** Bug 328779 has been marked as a duplicate of this bug. ***
I am not sure why the recursive magnification bug is a duplicate of this one, can someone clarify?
> KMag needs to be in an area where no window can be beneath it, > for example in a bar at the top or any other screen edge. Exactly this idea has already been implemented in the KDE3-based KMag (see https://invent.kde.org/accessibility/kmag/-/commit/1884b51a07f4a7a4d28bb325e4664e0bdc8802b6). That old version is quite easy to get running these days to test how it works (it needs more CPU than a Qt5-based KMag, though), let me know if you need some pointers to get started. The Qt4 port was branched off earlier than that commit and unfortunately was never forward-ported, which is why the Qt5-based KMag does not include it. Still, the code it out there and "only" needs porting. (Incidentally, the recursion issue mentioned above has also been fixed two times: Once in the Qt3 branch, and also in the Qt4 branch in a seemingly independent effort.)