llGetSex()

If it's in the interface, we should have script access to it. I say make getters/setters for everything in Appearance.

But finishing script access to object attributes should be more important.

By 'we' I mean simply the system as a whole-- SL has existed without this. I'm not making statements about possible positive uses about it. I'm sure they exist.



Where do you see LL-bashing? Certainly not from me. I made a statement about SL, not Linden. Let me reiterate in manner that will perhaps be less confusing:

SL has begun attracting users who have little to contribute beyond the trite values they epouse. There, Is that clear enough?

Thank you Peter Notron.

thats the problem guys... this is exactly what *you* are doing :/

i don't think this is a needed function myself too.. i think LL has better things to do... but seriously yer basically yer espousing yer values and stomping all over someone's question with them...

if yer against it too guys.. a no with the simple warning 'it could be abused' suffices... stomping is somethin i know both michi an chromal you both want less of in game :/

[/B]

Okay, I'm letting this get out of hand. For that, I'm sorry to anyone who has read this far in. Nothing constructive will come from statements like my own, quoted above.

I made my point pretty umambiguously two or three posts ago, there's really nothing for me to add. I hope it all works out for the best, whatever that might be.

There does not have to be a new llGetGender() method. A much more consistent approach is a DATA_GENDER constant for use with llRequestAgentData().

The problems with statements like these is that they are implying that we have no way to do this within the current LSL featureset.

There is, and Jack Digeridoo fails to see this approach as reasonable.

I have discussed this approach earlier in the thread.

I really dont understand why Jack feels that it is unintuitive. Allowing users CHOICE *is* intuitive. The way you implement how your script reflects that choice is up to you. You can make it astoundinly unintuitive, asking the same user for their gender with each and every action that relates to it, or you can cache or broadcast the result, which allows an interface almost as seemless as having an llGetSex API call would be.

If your object entails two objects communicating with each other, broadcast the result of the user's choice to objects around the user, and allow objects interacting with the user's object to ask the user's object (not the user, *that* would be redundant) what the user's gender is.

Its all a matter of how lazy you want to be.

I totally agree. you gotta admit, llGetSex is sexy though.

Just sell two products you will sell more. I'm not fond of the idea of a command to get gender in any form. It seems to me to be an invasion of privacy. In RL they don't look down your pants to see which catagory you fall into; SL should be no different. If you want to know, ask.