On Tue, Jun 06, 2023 at 02:12:50PM -0400, Maxim Cournoyer wrote: > I researched the problem and found that the feature I wanted was implemented > using XTest, which is detected at wxWidgets' build time [1]. Looking at the > Debian > package dependencies, I found it did *not* depend on the libxtst6 package. > > [1] https://github.com/wxWidgets/wxWidgets/issues/17530
Have you actually tested a wx build with this enabled? Comments in that ticket suggest that XTest doesn't work on Wayland and "Wayland is used by default in Debian 10 and newer" (10 is buster, the current stable release right now which is about to become oldstable): https://wiki.debian.org/Wayland It looks like there isn't a Wayland-specific implementation in the source and src/unix/uiactionx11.cpp uses X11-specific functions so building with --with-xtest may not really solve your problem. Forcing use of X11 for the app may help, e.g.: GDK_BACKEND=x11 ./myapp (The debian wx packages currently effectively do the above automatically if wxGLCanvas is used as the current support for wxGLCanvas on Wayland has some problems - hopefully we can eliminate that soon, but it seemed the least risky fix for the bullseye release.) > * What was the outcome of this action? > > This bug/wishlist report. Hilarious, but more useful answers to these questions would be a short python script to allow us to easily check if wx.UIActionSimulator is working as you expect or not (e.g. currently this script produces no output, with working support it should output "..."). > wx.UIActionSimulator from wxPython/wxWidgets should produce key inputs > instead of nothing. It should work like it does on Guix System. I notice that configure --help describes this feature as "experimental": --enable-uiactionsim use wxUIActionSimulator (experimental) That might be an outdated status though. Cheers, Olly
