Pablo Tesone

I have done a check on this issue. The same is happen when using the OpenSource alternative App Rectangle. These applications are using Accessibilities features to interact with the other...

I have checked how Firefox is resolving this in the Gecko project (their multiplatform UI Fwk) but they are using deprecated API to perform this (or at least the version...

Gecko Code https://github.com/mozilla/gecko-dev/blob/master/accessible/mac/Platform.mm GitHubgecko-dev/Platform.mm at master · mozilla/gecko-devRead-only Git mirror of the Mercurial gecko repositories at https://hg.mozilla.org. How to contribute: https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html - gecko-dev/Pl...

Also a useful hint, it is easy to debug the app with the **Accessibility Inspector** that comes with XCode. https://developer.apple.com/library/archive/documentation/Accessibility/Conceptual/AccessibilityMacOSX/index.html#//apple_ref/doc/uid/TP40001078

@fedemennite @VincentBlondeau Can you tell me if you see an improvement with it? Thanks.

@demarey I think it has to do with the change we integrated yesterday. I will check it, if you can see it also, it will be great.

> @guillep there's a problem with this approach. The changes in [pharo-project/pharo-vm#444](https://github.com/pharo-project/pharo-vm/pull/444) require using a `Pharo11` image. > > I guess we could backport the changes needed to support SIMD...

~~I want to add the setting from outside the image format to use. Please don't merge yet.~~

If you are getting from the Win32 API they are not valid UTF16 strings, they are multibyte but the encoding it is different, We should use Win32WideString to decode them...

I changed the access to the Environment entries to use GetEnvironmentStringsW, and then all strings we are sure that they are Win32WideStrings. If we use the ASCII version, it might...