-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HYDRA-1036 : Refactor Repr Selector Scene Index to send Dirty Notification #153
HYDRA-1036 : Refactor Repr Selector Scene Index to send Dirty Notification #153
Conversation
…d of repeated Add/Removal of prims
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, but needs a test to demonstrate that no notifications are sent for prims added / removed, and that the only notifications are for dirtying, with the appropriate data source locators.
SceneIndexNotificationsAccumulator notifsAccumulator(sceneIndices.front()); | ||
|
||
// Set wireframeOnShaded mode | ||
MString wireframeOnCmd = "select -cl; modelEditor -e -wireframeOnShaded 1 modelPanel4; refresh;"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bit of a nit-pick, and there's nothing really wrong with this, but you could have done the
select -cl; modelEditor -e -wireframeOnShaded 1 modelPanel4
(the Python equivalent of it) in testSceneIndexDirtying.py, and here used the C++ API:
MString wireframeOnCmd = "select -cl; modelEditor -e -wireframeOnShaded 1 modelPanel4; refresh;"; | |
M3dView view; | |
M3dView::getM3dViewFromModelPanel(MString("modelPanel4"), view); | |
view.refresh(/* all = */ true); |
…irtyingNotification
The change avoids removal/addition of Hydra prims and instead allowing dirty notification being sent to Hydra.