 | | | skip COP update when PPG parameter changes | skip COP update when PPG parameter changes 2004-07-07 - By Aloys Baillet
Back
No you're not missing anything... I checked this morning and actually I
keep the dataset in memory between the operator calls...
My operator is a Curve operator and the curve dataset is lighter, that's
why I keep it (even if I generate a curve list of 50000 control points!).
So please forget what I said yesterday...
--
Aloys Baillet - R&D @ La Maison
--
Felix Gebhardt wrote:
>Unfortunately I have an empty polymesh on the In Port. The data gets
>generated in the operator.
>
>In case I'm missing something very obvious with the Input Port just pretend
>I didn't say anything,
>Felix
>
>
>
>Aloys Baillet wrote:
>
>
>>Indeed, I had the same problem, but to avoid that, I copy the big
>>dataset from the Input Port to the Output Port just before leaving the
>>Operator. And I don't need to cach it, but it take some time to
>>update... I also implemented a autorefresh state with a refresh button.
>>That helps...
>>But the Button idea is a good one!
>>Cheers too!
>>
>>--
>>Aloys Baillet - R&D @ La Maison
>>
>>
>>
>>>Hi again Aloys,
>>>
>>>that's what I meant with catching it in the operator and I did just what
>>>you did. The problem is it's a mesh generator and if I return early the
>>>object reverts to its pre-operator state. This is just an cosmetic
>>>thing, agreed, but in the next update it computes the whole thing for
>>>some time while looking odd and a possible user might think the plug-in
>>>crashed. Caching the last valid result is not an tempting solution
>>>either since the dataset might be really big.
>>>
>>>What I did in the end was to create a whole row of buttons for some
>>>reasonable ratios. Not pretty but better than the confusing odd-state.
>>>
>>>Cheers, and thanks for your help.
>>>Felix
>>>
>>>
>>>Aloys Baillet wrote:
>>>
>>>
>>>
>>>
>>>>Hello again Felix!
>>>>I had the same problem today and here is the only solution I found :
>>>>Let's say that I have a CPSet with a parameter named "Preset".
>>>>Everytime my operator is called, I check the value of "Preset" and the
>>>>value of the UserData attached to the UpdateContext of my Operator. If
>>>>they are the same, I let my operator compute the big thing, if not, I
>>>>just return. And I don't forget in both cases to set my UserData to the
>>>>value of the Preset param before leaving the Op!
>>>>Of course you can keep track of many parameter values you don't want
>>>>they trigger the Operator, store it in a structure and then store the
>>>>structure in the UserData!
>>>>Hope this will help you...
>>>>
>>>>--
>>>>Aloys Baillet - R&D @ La Maison
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Is there a way to have a parameter change in a PPG not update the
>>>>>operator? I have two parameters basically saying the same interlinked
>>>>>via SPDL logic. The one is an explicit number, the other a ratio
>>>>>computing the explicit number for the user. Now if I set the ratio
>>>>>changing the number with a OnChange sub the operator updates twice.
>>>>>Since the operation is a bit intense I don't want this to happen.
>>>>>Catching it in the operator does not work without having the mesh
>>>>>revert to it's original state in the empty cycle or overhead nearly
>>>>>the same as a full update.
>>>>>
>>>>>Any ideas?
>>>>>F.
>>>>>
>>>>>---
>>>>>Unsubscribe? Mail Majordomo@(protected) with the following text in
>>>>>body: unsubscribe xsi
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>---
>>>>Unsubscribe? Mail Majordomo@(protected) with the following text in
>>>>body: unsubscribe xsi
>>>>
>>>>
>>>>
>>>>
>>>---
>>>Unsubscribe? Mail Majordomo@(protected) with the following text in
>>>body: unsubscribe xsi
>>>
>>>
>>>
>>>
>>>
>>>
>>---
>>Unsubscribe? Mail Majordomo@(protected) with the following text in body:
>>unsubscribe xsi
>>
>>
>
>---
>Unsubscribe? Mail Majordomo@(protected) with the following text in body:
>unsubscribe xsi
>
>
>
>
---
Unsubscribe? Mail Majordomo@(protected) with the following text in body:
unsubscribe xsi
|
|
|