-
Notifications
You must be signed in to change notification settings - Fork 13
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
[Suggestion] Auto Record feature #41
Comments
Definitely an interesting thought. Start/Stop can be a little tricky to narrow down apart from specific scenarios (like running a program or starting a debug session). Starting with listening to debug/run sessions should be doable. The tricky part is figuring out how to configure the behavior on a per execution target basis |
Hey @damsdev1, took a look at the PR. Hooking into debug start/stop should be easy enough, the challenge will be determining when the user is expecting that behavior and how to express that. I'm contemplating adding a field to the Launch Config to indicate if a recording session should be created. The other option is to automatically detect the start, and then with a one-time request, ask if future runs of the launch target should produce recordings. |
Sounds good, just need to add to that a command to activate/deactivate by workspace, and I think that would be nice. |
This feature would allow the recording to be triggered automatically when an activity is detected on VSCode (recording, saving files, debugging, etc), and if after a certain time in seconds (customizable) no activity is detected on VSCode, we stop the recording. (Like Wakatime do https://github.com/wakatime/vscode-wakatime/blob/master/src/wakatime.ts)
This new feature could be activated per project (folder) with a command, or globally, maybe.
The text was updated successfully, but these errors were encountered: