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
{{ message }}
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
During debugging of some other things I noticed that directly after Maya launch the mayalookassigner dialog actually has initialized and started. Which seems redundant before the user clicked on the actual "launch maya look assigner".
It seems extra off that it's a top level widget maybe? I thought it wasn't a top level widget if it were parented to Maya main window?
Some more details
I noticed that when commenting out this avalon.on("init", on_init) line the mayalookassigner tool doesn't show up in that list when printed. Meaning it's some code triggered through there causing it which I traced down to override_toolbox_ui because removing that also fixes it.
It feels off that even checking whether it's available actually initializes the dialog. Shouldn't it just be a case of checking whether mayalookassigner tool is availble (at most check whether we can access it on our pythonpath?)
Aside of that with Maya Look Assigner code now inside OpenPype this seems like less required? (However, it was also in openpype.tools.mayalookassigner during that commit).
Initialize the app only when the user starts it instead.
Additional context
I understand It's a bit extreme to focus on this since it doesn't really get in the way. But making sure apps don't unnecessarily slow down host start ups etc. I felt it would be good to at least open this issue here. This also should give us extra focus so that we ensure not all OpenPype tools get initialized in the background on Maya start making it drag down over the years as we expand the toolset.
[cuID:OP-2445]
The text was updated successfully, but these errors were encountered:
Describe the bug
During debugging of some other things I noticed that directly after Maya launch the mayalookassigner dialog actually has initialized and started. Which seems redundant before the user clicked on the actual "launch maya look assigner".
It seems extra off that it's a top level widget maybe? I thought it wasn't a top level widget if it were parented to Maya main window?
Some more details
I noticed that when commenting out this
avalon.on("init", on_init)
line the mayalookassigner tool doesn't show up in that list when printed. Meaning it's some code triggered through there causing it which I traced down tooverride_toolbox_ui
because removing that also fixes it.Which is when I traced it down to here. Looking at that code makes somewhat sense as to why it happens - it's trying to not add the maya look assigner button if it can't be initialized.
It feels off that even checking whether it's available actually initializes the dialog. Shouldn't it just be a case of checking whether
mayalookassigner
tool is availble (at most check whether we can access it on our pythonpath?)Aside of that with Maya Look Assigner code now inside OpenPype this seems like less required? (However, it was also in
openpype.tools.mayalookassigner
during that commit).To Reproduce
Steps to reproduce the behavior:
Confirm the dialog exists:
Expected behavior
Initialize the app only when the user starts it instead.
Additional context
I understand It's a bit extreme to focus on this since it doesn't really get in the way. But making sure apps don't unnecessarily slow down host start ups etc. I felt it would be good to at least open this issue here. This also should give us extra focus so that we ensure not all OpenPype tools get initialized in the background on Maya start making it drag down over the years as we expand the toolset.
[cuID:OP-2445]
The text was updated successfully, but these errors were encountered: