Information seems to be somewhat scarce, but based on the description of knob_change_finished, it sounds a bit like the knob (or the callback) isn’t functioning properly in that respect.
-Nathan From: Ivan Busquets Sent: Monday, May 13, 2013 12:38 AM To: Nuke plug-in development discussion Subject: [Nuke-dev] knob_change_finished unexpected behaviour with Box3_knob Hi, I'm trying to prevent a Box3 knob from changin the hash (and triggering a re-render) while the user is dragging around the 3D handles, and only do so once the handle is released. My plan was to set/unset a NO_RERENDER flag to the knob, and force the update only when knob_change_finished() is called. However, knob_change_finished() is called just as frequently as knob_changed() on a Box3 knob. As in, it is called while dragging the 3D handles. Before I send an email to support, I thought I'd fish for some tips/advice here. Are there any other strategies I could use to achieve this? The goal is to have a Box3 behave like a Transform2D node (no processing done while dragging the widget/handle in the viewer) Thanks in advance, Ivan -------------------------------------------------------------------------------- _______________________________________________ Nuke-dev mailing list Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
_______________________________________________ Nuke-dev mailing list Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
