Re: PPGEventContext Object "Inspected" & "InspectedObjects"

Date : Tue, 10 Oct 2006 16:10:39 +0100
To : XSI(at)Softimage.COM
From : "Alan Jones" <skyphyr(at)gmail.com>
Subject : Re: PPGEventContext Object "Inspected" & "InspectedObjects"
Actually C++ has another advantage too - I made a custom property
which has dynamic buttons, tabs etc. I'm not sure it would even have
been possible with scripting because you need to know the name of the
button to write the function, but with C++ it's just one function
which is called and you check the name of the button which called it -
this made it really easy to create dynamic datasets when combined with
grids.

Cheers,

Alan.

On 10/9/06, Luc-Eric Rousseau <lucer(at)softimage.com> wrote:


Well it's sadistic in the sense that the amount of code that you need to
write in scripting for spdl logic is much smaller.  When a callback is
called, a virtual object is inserted in the script namespace which
represents the property page but also its multiple-selection support.   So
when you do "property = value" it is in fact that proxy object which
magically makes that setvalue happen to all the object in the multiple
selection, exactly like changing the slider in multiple-select does. The
notation to access stuff is generally smaller as well.

-----Original Message-----
From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM]On Behalf Of
Aloys Baillet
Posted At: Monday, October 09, 2006 2:03 AM
Posted To: xsi
Conversation: PPGEventContext Object "Inspected" & "InspectedObjects"
Subject: Re: PPGEventContext Object "Inspected" & "InspectedObjects"

Hi Andrea,

Sorry, but I don't think you are a sadistic...
C++ custom properties are amazingly fast compared to the scripted ones. I
even suspect that they are faster than SPDL-based ones...
Inspecting a C++ custom property is just instantaneous.
And the fact that there is only one callback for all PPGEvents is a blessing
when you have to create a custom properties with a dynamic number of buttons
and/or parameters.
But you're right, there is a bug in the implementation: there is no way from
a C++ custom property PPGEvent callback to retrieve all inspected custom
properties concerned by the current event.
Let's say we were to implement a custom property similar to the Direction
Constraint property, where the user can click on the small "X", "-X", etc.
buttons to quickly set parameter values from the axis presets. In "multi"
PPG mode, clicking on one of these buttons would not update all the
inspected properties, but only the first one, which is not the desired
behavior!
I'll log this as a bug to Softimage, and Andrea, if you want, you can do the
same so that we can get that fixed.

Cheers,

Aloys


---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi


Search the XSI List archives here or use the advanced search form to search across mailing lists. Searching help is available.
This site supposedly brought to you by Benjamin Grosser and the Imaging Technology Group.