Open Fivefold opened 3 years ago
Hi there! As you're new to this repo, please make sure you've used an appropriate issue template and searched for duplicates (it helps us focus on actual development!). We'd also like to suggest that you read our contribution guidelines and our code of conduct. Thanks a bunch for opening your first issue! 🙏
I think the screenshot is of the Linux build which does not have the same method of fetching the application name. The behavior you have is expected on windows I believe.
hi, im having this issue too on windows 11 please lmk if you want me to provide you with logs
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Yes, it would be good to have the name/title show on Windows. I have the same issue with firefox.exe. When using different builds (like standard and developer edition), they all get reported as 'firefox.exe' so can't categorize them separately. Only work around so far was to rename the executable file so it the regex filters would be able to catch it. Not ideal as each time it gets updated I need to rename the file. If the window names were reported then one could categorize the different windows even though they are running under the same process name.
Describe the bug
Not sure if this is actually a bug or intended behaviour, but the official screenshots imply otherwise. For window titles
aw-watcher-window
seems to log the process names (e.g.firefox.exe
instead ofFirefox
). This also affects category matching, e.g. (case-sensitive)Firefox
won't match the firefox application, butfirefox.exe
or (case-sensitive)firefox
will.This is on a fresh install.
Maybe it's relevant, I installed ActivityWatch using chocolatey https://community.chocolatey.org/packages/activitywatch
Expected behavior
Show the window titles as shown in the official screenshots.
Documentation
Additional context
I found errors in the aw-watcher-window logs but don't think they are related:
There's more identical OLE errors
Maybe those relate to the "unknown" application.