You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In development mode, when you make a change to a talon hud walkthrough (either a markdown or a json walkthrough, it doesn't matter which) Talon HUD walkthrough widgit freezes, loses all text, is unresponsive to mouse clicks and drags, and forces a complete restart of Talon.
Expected behavior is to update the walkthrough step with the change.
The temporary fix:
commenting out the progress bar code, and specifically, lines 418 to line 422, in walkthroughpanel.py makes it so that any changes to a walkthrough appear immediately after saving the change.
This makes everything function normally at the cost of disabling the progress bar. Progress bar can be re-enabled when you are not in development mode.
Bug reproduction
On windows 10:
after saying head up develompent start
open any walkthrough
Open any walkthrough in vscode
make a change to the walkthrough file in vscode
The walkthrough panel will turn blank, become unresponsive, and refuse voice commands and mouse clicks
The Problem
In development mode, when you make a change to a talon hud walkthrough (either a markdown or a json walkthrough, it doesn't matter which) Talon HUD walkthrough widgit freezes, loses all text, is unresponsive to mouse clicks and drags, and forces a complete restart of Talon.
Expected behavior is to update the walkthrough step with the change.
The temporary fix:
commenting out the progress bar code, and specifically, lines 418 to line 422, in walkthroughpanel.py makes it so that any changes to a walkthrough appear immediately after saving the change.
This makes everything function normally at the cost of disabling the progress bar. Progress bar can be re-enabled when you are not in development mode.
Bug reproduction
On windows 10:
head up develompent start
The following error appears in the log
The text was updated successfully, but these errors were encountered: