I regularly work with multiple VS Code windows open at the same time with different projects. Most of the time they are separate VS Code Workspaces but sometimes just an opened folder and almost never a normal new window. Below are three examples of how this is shown in the window title:
Folder:
Workspace:
New Window:
The Watcher should always check if the current window is an opened worspace or folder and should make heartbeats accordingly. Otherwise the different heartbeats to the same bucket from different open windows would override each other which results in an unusable timeline, meaning very tiny activity "blips". (hostname pixelated):
These new buckets per project could be created automatically, but it would also be fine if an error shows that the bucket doesn't exist and the user needs to use the Reload ActivityWatch action manually.
I regularly work with multiple VS Code windows open at the same time with different projects. Most of the time they are separate VS Code Workspaces but sometimes just an opened folder and almost never a normal new window. Below are three examples of how this is shown in the window title:
Folder:
Workspace:
New Window:
The Watcher should always check if the current window is an opened worspace or folder and should make heartbeats accordingly. Otherwise the different heartbeats to the same bucket from different open windows would override each other which results in an unusable timeline, meaning very tiny activity "blips". (hostname pixelated):
These new buckets per project could be created automatically, but it would also be fine if an error shows that the bucket doesn't exist and the user needs to use the
Reload ActivityWatch
action manually.