This means that the function ViewerDelegate::getAttributes() will return these manipulated values so that the Viewer can present interactive performance. This allows setValue() to set attributes rather than parameters directly.īecause the cooking times can be non-interactive in certain scenes, the Manipulators use a mechanism that will make the ViewerDelegate to return the manipulated values while the cook is running. This is done via the setValue(), which follows a protocol used by Katana that maps Scene Graph attributes with nodes and parameters in the current project. When interacting with a Manipulator Katana will be informed that something changed and needs to potentially be stored in a node attribute and recooked. If there are ManipulatorHandles being used then draw() and event() will be propagated by each one of them. The draw() and event() functions can implement all the drawing and UI event handling without using any ManipulatorHandle. Typedefs typedef std :: shared_ptr ManipulatorWrapperPtr ¶Ĭlass Foundry :: Katana :: ViewerAPI :: ManipulatorPluginBase ¶Ī Manipulator allows a user to interact with the Viewer scene by drawing handles that can be interacted with and that can change values in the scene.Ī Manipulator can be optionally composed of a series of ManipulatorHandles, which are a plug-in type on its own to allow reusability between Manipulator types. Designing Node Graphs for Optimal Performance.Profiling and Optimization Guide: Start Here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |