[Opensim-dev] ScenePresence.FlyDisabled property

[Justin Clark-Casey]

Teravus Ovares wrote:
> RE: Difference in FlyDisabled vs FlyUnavailable,
> I'm thinking that FlyDisabled would be used for a specific purpose in
> a module and it wouldn't necessarily depend on the land or region
> settings..  where FlyUnavailable would.

Ah, so stop certain people from flying (or alternatively, only allow certain people to fly).

> 
> Regards
> 
> Teravus
> 
> On Thu, Aug 6, 2009 at 2:59 PM, Justin
> Clark-Casey<jjustincc at googlemail.com> wrote:
>> Teravus Ovares wrote:
>>> Hey there
>>>
>>> I was exploring ScenePresence looking for a way to add a feature to
>>> enforce 'no fly' serverside and I noticed that there's a property
>>> 'FlyDisabled' that isn't obviously used.   Now, I know that just
>>> because OpenSimulator doesn't explicitly use a public property doesn't
>>> mean that it isn't used at all.  It could be used by a module.
>>>
>>> So, I'd like to have a server side option that enforces no-fly server
>>> side (which means that clients cannot directly fly..   they can 'look'
>>> like they're flying with the client button, but it won't have an
>>> effect on the server).    I'm thinking the best way to proceed would
>>> be to have a method called by the 'Significant Movement' method to
>>> check the parcel and region settings and set a simple boolean property
>>> to check in the HandleMovement code.    FlyDisabled seems appropriate,
>>> however, if it's used by client applications in some way that's
>>> different then using FlyDisabled may interfere with that application
>>> of the property..  so it would be better to create another one called
>>> FlyUnavailable or something like that.
>> How would FlyDisabled be different from FlyUnavailable?  The FlyDisabled property has no documentation.  If we do end up
>> with two properties, could we document in the code the differences between the two?
>>
>>> If I don't hear from anyone, just to be safe, I'll create another
>>> property....     but if someone that is using that property lets me
>>> know that it's appropriate for what I'm thinking, I'd prefer to reuse
>>> it to keep the code from complexity bloat.
>>>
>>> Let me know :)
>>>
>>> Teravus
>>> _______________________________________________
>>> Opensim-dev mailing list
>>> Opensim-dev at lists.berlios.de
>>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>>>
>>
>> --
>> justincc
>> Justin Clark-Casey
>> http://justincc.wordpress.com
>> _______________________________________________
>> Opensim-dev mailing list
>> Opensim-dev at lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>>
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
> 


-- 
justincc
Justin Clark-Casey
http://justincc.wordpress.com