I think I asked Abhishek to take a look.

-phil.

On 2/10/25 2:41 PM, David Alayachew wrote:

Poke.

Any new info?


On Fri, Jan 17, 2025, 8:05 AM David Alayachew <[email protected]> wrote:

    Hello Phil,

    Did you get any more info about this issue?


    On Tue, Dec 17, 2024, 11:58 AM David Alayachew
    <[email protected]> wrote:

        Thanks Phil.

        Yeah, I am A-OK as long as this something that is looked into
        and the JBS Bug Report is updated with the findings. If this
        isn't too bad, this would be a solid inclusion. But if it's
        not worth the effort, I just want the JBS to be updated, and
        then I can put that as an answer for my StackOverflow post.

        Thanks again for taking a look into this.

        On Tue, Dec 17, 2024 at 11:56 AM Philip Race
        <[email protected]> wrote:

            Perhaps .. if it is an easy fix but I do not know the
            specifics and the evaluator of that bug wrote
            "the magnifier cannot receive PropertyChangeEvents from
            Swing. This is a limitation in the Window magnifier.
            The Windows magnifier could be modified by Microsoft to
            receive such events but the work would need to be done by
            Microsoft."

            then went on to add that other magnifiers do work ..

            I also don't know how tied in this would be to
            implementing support for the Windows Accessibility API.

            Swing apps today use something called JavaAccessBridge and
            there are screen readers out there that support it.

            It would be good to have another look at this specific
            issue, but I can't make any promises.

            -phil.

            On 12/15/24 1:04 PM, David Alayachew wrote:
            Hello Client Libs Dev Team,

            My eyesite has started to deteriorate significantly, so I
            have been using the built-in Accessibility tool called
            Windows (Screen) Magnifier (available since Windows XP at
            least). It zooms in and out of the screen by pressing the
            Windows Key and (+) or (-).

            This works great because, as I type stuff, the magnifier
            will follow my text, so that I don't have to keep
            manually moving the magnifier whenever what I type
            inevitably ends up off-screen (off-view?).

            This feature works great for basically every other
            application I have, except my Swing apps. I make a lot of
            Swing apps, and I use a bunch too. And this Magnifier
            feature that follows text does not work for any of the
            ones I have tried.

            This feature does work on basically every other
            application I have. To name a few.

            * Notepad++
            * WordPad
            * Firefox
            * Git Bash

            Here is a Bug Report referring to this problem.

            https://bugs.openjdk.org/browse/JDK-5079680

            The resolution was listed as "Future Project". Any chance
            that the future can be now?

            I know that Swing is largely in maintenance mode, but if
            this were to get added, practically ALL Swing apps would
            receive a significant boost in accessibility. I think
            that's worth making some significant changes for.

            Finally, here is a StackOverflow post I made discussing
            the same subject.

            https://stackoverflow.com/questions/79281778

            Thank you for your time.
            David Alayachew

Reply via email to