-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
Configurable available and autostart modules #47
Labels
Comments
wolferCZ
added a commit
to wolferCZ/aw-qt
that referenced
this issue
Nov 6, 2019
…ivityWatch#47 NOTE: `ConfigParser` does not correctly store array values. Store module lists as json.
Seems like a duplicate of #35? |
🤦♂️ Yes, my bad. |
xylix
pushed a commit
to xylix/aw-qt
that referenced
this issue
Mar 3, 2020
…ivityWatch#47 NOTE: `ConfigParser` does not correctly store array values. Store module lists as json.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a developer I would like to integrate my private watchers to the
aw-qt
without necessity to alter theaw-qt
and maintain my own fork.Currently
aw-qt
(v0.8.0b9) supports only few modules that are hard-coded in:aw-qt/aw_qt/manager.py
Line 129 in fcb5926
Posible solutions:
Based on TODO in
aw-qt/aw_qt/manager.py
Line 127 in fcb5926
aw-qt
configuration.aw-qt
configuration.NOTE: Available modules can be separated to independent issue/story (nice to have).
The text was updated successfully, but these errors were encountered: