TorqueXmlSchemaType and enum values

#1 Hi Ron,

TXB assumes as default value the first item in the enum, so be sure to have it corresponding to the desired default value, like this:

public enum MyStateEnum
{
    DefaultValue,
    Zero,
    One,
    Two,
    Three
}

private MyStateEnum _myState = MyStateEnum.DefaultValue;

public MyStateEnum MyState
{
    get
    {
        return _myState;
    }
    set
    {
        _myState = value;
    }
}

The above code gives you the desired result ;)

Pino

#2 Thanks, Pino...the only problem with this is that it is not a custom Enum that I have created. It is the enum for the Particle Effect modes (Infinite, Cycle, Stop, Kill).

The other problem is that the default value would/could change for different components. So in the case of destructible components, the default value might be "KILL" for objects that have been destroyed.

But for another object that issues a constant particle stream, the default value might be "INFINITE." So I could modify the enum in the source code for TX, but that doesn't really solve my problem.

Consider this:

[TorqueXmlSchemaType(DefaultValue = "1.0")]

and:

[TorqueXmlSchemaType(DefaultValue = "500.0")]

Both of these are floats, but the default values are different.

I need something like this for one component parameter:

[TorqueXmlSchemaType(DefaultValue = "KILL")]

and something like this for another component parameter:

[TorqueXmlSchemaType(DefaultValue = "CYCLE")]

TX doesn't seem to allow for this.

Hope that clarifies my question. Thanks for the help though!
--RB

#3 I've used stuff like [TorqueXmlSchemaType(DefaultValue = "Centered")] with no problems.

[TorqueXmlSchemaType(DefaultValue = "Cycle")] should work just fine. Be aware that Enums are case sensitive though and in your above code you are putting it entirely in upper case.

#4 @Duncan

Hmmm...I'm not sure if I tested all variations of character case, but I got assertion failures from TX for each particle effect that loaded. The assertion failure indicated that it was unable to convert the string value to the appropriate enum type value. This was odd to me, because I was pretty sure that native C# is able to do this conversion.

I had seen something like this in the past where I was setting values for objects that had not yet been registered, and TX didn't like that (resulting in the same assertion failure message).

I'll verify that I tried the appropriate case as defined in the TX source code (but I think I would have tried that).

I'll post my findings after I verify the case tonight.

Thanks for the responses!
--RB

#5 Thanks, Duncan.

Major rookie mistake. I guess of all the things I tried, I never tried assigning the exact case as is defined in the enum.

I think I got confused by the fact that in TXB, when creating/editing a particle, the pull down to set the type is in solid caps.

Assertion failure is gone...default values are appearing as expected.

Thanks
--RB