We have a feature to show the current value of a variable on hover, like in the Godot script editor. We already have the debugger/variables panel showing the current state of the variable at runtime.
The version on mouse hover in the code listing is not very intuitive because it doesn't have the same labeling. It creates also many underlines that don't really help with readability. It only adds an alternate way to get the same information as the debugger/variables panel. So I personally don't see its purpose anymore.
In the Godot editor, the variables do not get underlined. You just have to know that you can hover over them, which works a little better and makes more sense from within Godot itself, because the debugger has tons of information, and you might want to preview the value of a single variable.
One reason I think we had it in this app was that it appeared useful to someone already experienced, and also we had the debugger thing below the code as a separate panel, easier to miss or misunderstand.
This image shows the updated runnable example layout from #1401 with the mouse hovering over the health variable in the code listing:
We have a feature to show the current value of a variable on hover, like in the Godot script editor. We already have the debugger/variables panel showing the current state of the variable at runtime.
The version on mouse hover in the code listing is not very intuitive because it doesn't have the same labeling. It creates also many underlines that don't really help with readability. It only adds an alternate way to get the same information as the debugger/variables panel. So I personally don't see its purpose anymore.
In the Godot editor, the variables do not get underlined. You just have to know that you can hover over them, which works a little better and makes more sense from within Godot itself, because the debugger has tons of information, and you might want to preview the value of a single variable.
One reason I think we had it in this app was that it appeared useful to someone already experienced, and also we had the debugger thing below the code as a separate panel, easier to miss or misunderstand.
This image shows the updated runnable example layout from #1401 with the mouse hovering over the health variable in the code listing: