You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using PyAutoGUI is once again turning us into the second wagon, having to deal with all their decisions (and lack of such) like not providing easy setup for Fedora (or responding to issues and proposal to help providing them), making their product a more preferred choice for people needing simple headless display control instead of directly competing with it, and not being able to easily do something about deep display controller issues like dropped keys and/or mouse clicks.
Adopting the now abandoned rust-based AutoPy (now gradually dropped by everyone that used to depend on it) can provide us with a ready-made solution for our own display controller and a base for further development in Rust regarding the Guibot project.
The text was updated successfully, but these errors were encountered:
Using PyAutoGUI is once again turning us into the second wagon, having to deal with all their decisions (and lack of such) like not providing easy setup for Fedora (or responding to issues and proposal to help providing them), making their product a more preferred choice for people needing simple headless display control instead of directly competing with it, and not being able to easily do something about deep display controller issues like dropped keys and/or mouse clicks.
Adopting the now abandoned rust-based AutoPy (now gradually dropped by everyone that used to depend on it) can provide us with a ready-made solution for our own display controller and a base for further development in Rust regarding the Guibot project.
The text was updated successfully, but these errors were encountered: