I'm not sure if this is what is causing it for other scenarios, but I've
figured out what was causing it for me.
I have a script that is doling these Properties out onto scene objects, but
it is also changing their names to something different than the registered
PPG name:
SceneObject.AddProperty("MyCustomProp", 0, "DifferentName")
Even though all of the SceneObjects get a custom prop with the same exact
name, XSI treats them as if they are unique and doesn't give them Multi
Selection super powers.
If instead I leave out the 3rd Parameter in AddProperty:
SceneObject.AddProperty("MyCustomProp", 0)
I get appropriate PPG behavior with Multi Selection.
On Thu, May 10, 2012 at 5:44 PM, Dan Yargici <[email protected]> wrote:
> I've seen this many times too and would also love to know the reason!
>
> Eagerly awaiting any info...
>
> DAN
>
>
> On Thu, May 10, 2012 at 10:03 PM, Bradley Gabe <[email protected]> wrote:
>
>> I've noticed this before, and now it's happening with a custom tool kit
>> I've been developing.
>>
>> I have a simple Custom PPG defined in a self installing plugin and am
>> applying it to multiple objects in the scene. However, if I multi-select
>> the objects, the PPG doesn't show up at the top of the selection explorer.
>>
>> If I open the PPG on one of the objects, then multi select other objects
>> with the same custom property, the title bar of the PPG reads "[multi]",
>> but none of the multi selection features work... if I edit a parameter, it
>> only affects the first item in the selection.
>>
>> What gives? Is there a way to construct the PPG in order to avoid this
>> behavior? I really need them to work in multi-selection mode!
>>
>> -B
>>
>
>
