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
A draft implementation has been pushed just now for AskUserDialog. This is the fusionless class for Fusion's comp.AskUser. Consider it a draft implementation, so make sure to test the functionality once you start adopting it.
I'm not too fond of how Fusion returns some of the values from the dialog.
For example a position control returns the values as {1.0: 0.5, 2.0: 0.5, 3.0: 0.5}. So basically it is a dictionary with three values (even though the control shows only X, Y). Preferably I would have it return it as a list or tuple, like (0.5, 0.5, 0.5) (for X, Y, Z if the Z-component is shown in the UI which I haven't seen yet).
Furthermore I'm opening this issue to open up discussion about the overall implementation.
The text was updated successfully, but these errors were encountered:
This seems to work really well. I would like to suggest an optional argument for multibutton and dropdown controls to return the selected string value.
Implementation
A draft implementation has been pushed just now for
AskUserDialog
. This is thefusionless
class for Fusion'scomp.AskUser
. Consider it a draft implementation, so make sure to test the functionality once you start adopting it.An example of usage is available here: https://github.com/BigRoy/fusionless/blob/master/examples/comp/ask_user_dialog.py
The resulting dialog:
As far as I tested all functionality should work.
Discussion
I'm not too fond of how Fusion returns some of the values from the dialog.
For example a position control returns the values as
{1.0: 0.5, 2.0: 0.5, 3.0: 0.5}
. So basically it is a dictionary with three values (even though the control shows only X, Y). Preferably I would have it return it as a list or tuple, like(0.5, 0.5, 0.5)
(for X, Y, Z if the Z-component is shown in the UI which I haven't seen yet).Furthermore I'm opening this issue to open up discussion about the overall implementation.
The text was updated successfully, but these errors were encountered: