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
I'll cut right to the chase. I've either found behavior that's undesirable or I don't understand the intent behind it.
I assumed that the ID of a given tool or document dock is supposed to be unique, as I am then using it to locate the specific component. Like so: dock = dockLayoutFactory.GetDockable<EditorDocumentDock>(id);
I have run into an issue where I am unable to reasonably differentiate between document docks if the users decides to split the document dock into two.
Here's the relevant code from my Layout Factory that creates the new document dock and sets the ID:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, thanks for the hard work on the library!
I'll cut right to the chase. I've either found behavior that's undesirable or I don't understand the intent behind it.
I assumed that the ID of a given tool or document dock is supposed to be unique, as I am then using it to locate the specific component. Like so:
dock = dockLayoutFactory.GetDockable<EditorDocumentDock>(id);
I have run into an issue where I am unable to reasonably differentiate between document docks if the users decides to split the document dock into two.
Here's the relevant code from my
Layout Factory
that creates the new document dock and sets the ID:I have found that the ID is overwritten inside
DockManager.cs
within this library and is set based on the sourceDocumentDock:Am I approaching this in an unexpected way, or is this an oversight. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions