Is your feature request related to a problem?
I’m trying to make a system where a notification pops up if a certain variable is changed. While my issue is mainly that I don’t entirely understand how signals work, I still think it would be nice to show a pop up of what signals could be used for something, like variables or portraits/characters.
The solution you'd like
Hovering over a part of Dialogic (a character in the Dialogic scene tree, or a specific variable in the variable tab) will show what signals can support it. It could be like connecting a built-in signal (like connecting a button in a scene to a script). My main example is a custom variable and the “variable_changed(info:Dictionary)” signal. Attaching it to a script will automatically place in the signal and a way to detect if it’s been changed.
Alternatives you've considered
It could also work by showing off the signal with a short description like hovering over something in the inspector. This could be easier, and avoid problems my main idea could cause. Example, if you have a character called ‘Ted’, a hover could show ‘signal character_joined(Ted)’ (or however it should work, I'm still not sure myself and am trying to learn) then a short description of how it works.
Additional context
I think this could also help let the user know of any features they may have missed within the documentation. Also, apologies if any of this doesn’t make sense or I repeat things too often, I’m not very good at describing things but did the best I could. Hope it’s still understandable.
Is your feature request related to a problem? I’m trying to make a system where a notification pops up if a certain variable is changed. While my issue is mainly that I don’t entirely understand how signals work, I still think it would be nice to show a pop up of what signals could be used for something, like variables or portraits/characters.
The solution you'd like Hovering over a part of Dialogic (a character in the Dialogic scene tree, or a specific variable in the variable tab) will show what signals can support it. It could be like connecting a built-in signal (like connecting a button in a scene to a script). My main example is a custom variable and the “variable_changed(info:Dictionary)” signal. Attaching it to a script will automatically place in the signal and a way to detect if it’s been changed.
Alternatives you've considered It could also work by showing off the signal with a short description like hovering over something in the inspector. This could be easier, and avoid problems my main idea could cause. Example, if you have a character called ‘Ted’, a hover could show ‘signal character_joined(Ted)’ (or however it should work, I'm still not sure myself and am trying to learn) then a short description of how it works.
Additional context I think this could also help let the user know of any features they may have missed within the documentation. Also, apologies if any of this doesn’t make sense or I repeat things too often, I’m not very good at describing things but did the best I could. Hope it’s still understandable.