ActivityWatch (aw-watcher-window) can't trace windows tittles nor applications

[farodri78]

• [x] I am on the latest ActivityWatch version.
• [x] I have searched the issues of this repo and believe that this is not a duplicate.

• OS name and version: Windows 10 Pro + 22H2
• ActivityWatch version: v0.12.2

Describe the bug

ActivityWatch (aw-watcher-window) can't trace tittles on word, pdf viewer, winrar, winzip files, other king of files, if those files are open using "XY Explorer" instead of default windows file explorer.

To Reproduce

1. Go to 'XY Explorer', 2. Click on 'any folder', 3. Scroll down to 'any file, 4. See error: look into ActivityWatch Buckets and the program or file previusly opened is not detected/traced/watched by aw-watcher-window

Expected behavior

trace/ log the window title and record its event

Documentation

Additional context

This problem won't occur on Version: v0.12.1

[github-actions[bot]]

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! 🙏

[ErikBjare]

Does this "XY Explorer" run the apps with elevated permissions?

There has been a change in how we track the active window on Windows since v0.12.1 (which is much more performant, but does have this elevated process limitation).

I've been considering adding back the old method as a fallback, which would perhaps resolve the issue you're facing here as well.

[farodri78]

I tihink yes, in fact the problem also arise with office apps like world, excel, power point, acces, etc

F. Rodriguez

-------- Original message -------- From: Erik Bjäreholt @.> Date: 10/6/23 08:17 (GMT-05:00) To: ActivityWatch/activitywatch @.> Cc: farodri78 @.>, Author @.> Subject: Re: [ActivityWatch/activitywatch] ActivityWatch (aw-watcher-window) can't trace windows tittles nor applications (Issue #962)

Does this "XY Explorer" run the apps with elevated permissions?

There has been a change in how we track the active window on Windows since v0.12.1 (which is much more performant, but does have this elevated process limitation).

I've been considering adding back the old method as a fallback, which would perhaps resolve the issue you're facing here as well.

— Reply to this email directly, view it on GitHubhttps://github.com/ActivityWatch/activitywatch/issues/962#issuecomment-1750667888, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDCHZRAMCUTKBLXTXDS4363X6AAGPAVCNFSM6AAAAAA5UVXEE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJQGY3DOOBYHA. You are receiving this because you authored the thread.Message ID: @.***>