-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PyAutoGUI controller #21
Conversation
This pull request introduces 1 alert when merging 8a98505 into 4090679 - view on LGTM.com new alerts:
|
Codecov Report
@@ Coverage Diff @@
## master #21 +/- ##
==========================================
+ Coverage 80.21% 85.25% +5.03%
==========================================
Files 16 17 +1
Lines 4387 4400 +13
==========================================
+ Hits 3519 3751 +232
+ Misses 868 649 -219
Continue to review full report at Codecov.
|
8a98505
to
932d057
Compare
This pull request introduces 1 alert when merging 932d057 into dd17e65 - view on LGTM.com new alerts:
|
65bd61e
to
41b56f1
Compare
This includes dropping the platform-specific "desktop" in favor of the more platform-generic "display" for the DC backends as we could technically manipulate Android or other devices.
The controllers hierarchy taxonomy is now more readable and clearer, also in better accordance with the finder class hierarchy.
This requires also adding the necessary input (key, modifier, and mouse button) maps for the backend, in this case keyword strings.
The region tests that were the only ones doing this before only tested the default backend thus leaving a big gap in covering the alternatives that we compensate for here.
The default number of clicks should be one corresponding to a single click and writing unit tests for all backends revealed it wasn't so for some backends until now.
41b56f1
to
b87396d
Compare
This and the lack fo setting the base attribute was all discovered from the new unit tests.
Some methods with modifier args used a default None while others were still requiring the argument to be explicitly set, even if again to None.
It is simpler to just require a NOOP sync instead of requiring it for some backends and not for others, thus confusing the users and requiring them to know internal behaviors.
This is now done for all unit tests.
The following subbranch completes the unit test coverage undertaking from all recent branches by adding a final set of base unit tests for the display controllers.
An issue has been reported as the scrot support on Fedora is significantly lacking.
These coordinates are using during mouse initialization and are currently considered eligible.
This controller contains additional dependencies we haven't fully handled, hasn't been thoroughly tested, and is even unfinished, but contains valuable code that could be an example for how to derive a custom controller backend.
b87396d
to
908ff41
Compare
Add PyAutoGUI screen controller refactoring current controller state