Thanks guys,
Yes, I also noticed this comment in the Developer's Guide:
"A small subset of knobs have started supporting the
knob_changed_finished() method."
However, it does seem to be implemented for Box3 (and others, such as Float
and Int knobs).
My first guess was that the implementation might be flawed, but not having
dealt with knob_change_finished() before, I thought I'd ask here first.
I'll send an email to support.
Thanks,
Ivan
On Wed, May 15, 2013 at 11:25 PM, Nathan Rusch <nathan_ru...@hotmail.com>wrote:
> Yeah, I noticed that comment, but since it says the callback is only
> *triggered* by the BBoxKnob and he's dealing with a Box3 knob, I assumed
> that was some out-of-date documentation. Sounds like a support email is in
> order one way or the other though...
>
> -Nathan
>
> -----Original Message----- From: Ben Dickson
> Sent: Wednesday, May 15, 2013 11:09 PM
>
> To: Nuke plug-in development discussion
> Subject: Re: [Nuke-dev] knob_change_finished unexpected behaviour
> withBox3_knob
>
>
> I'm pretty sure the knob_change_finished is only implemented for certain
> knobs:
>
> grep -B2 knob_change_finished include/DDImage/Op.h
>
> // currently only triggered by the BBoxKnob but more will be supported
> in future.
> // Derived classes must return non-zero from this method if they want it
> to be called on that knob again.
> virtual int knob_change_finished(Knob* knob, bool changedByUser =
> true){return 0;}
>
>
> On 16/05/13 15:25, Nathan Rusch wrote:
>
>> 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 <mailto:ivanbusqu...@gmail.com**>
>> *Sent:* Monday, May 13, 2013 12:38 AM
>> *To:* Nuke plug-in development discussion
>> <mailto:nuke-dev@support.**thefoundry.co.uk<nuke-dev@support.thefoundry.co.uk>
>> >
>> *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 <Nuke-dev@support.thefoundry.co.uk>,
>> http://forums.thefoundry.co.**uk/ <http://forums.thefoundry.co.uk/>
>> http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/**nuke-dev<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev>
>>
>>
>> ______________________________**_________________
>> Nuke-dev mailing list
>> Nuke-dev@support.thefoundry.**co.uk <Nuke-dev@support.thefoundry.co.uk>,
>> http://forums.thefoundry.co.**uk/ <http://forums.thefoundry.co.uk/>
>> http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/**nuke-dev<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev>
>>
>
> --
> ben dickson
> 2D TD | ben.dick...@rsp.com.au
> rising sun pictures | www.rsp.com.au
> ______________________________**_________________
> Nuke-dev mailing list
> Nuke-dev@support.thefoundry.**co.uk <Nuke-dev@support.thefoundry.co.uk>,
> http://forums.thefoundry.co.**uk/ <http://forums.thefoundry.co.uk/>
> http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/**nuke-dev<http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev>
> ______________________________**_________________
> Nuke-dev mailing list
> Nuke-dev@support.thefoundry.**co.uk <Nuke-dev@support.thefoundry.co.uk>,
> http://forums.thefoundry.co.**uk/ <http://forums.thefoundry.co.uk/>
> http://support.thefoundry.co.**uk/cgi-bin/mailman/listinfo/**nuke-dev<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
