> I actually think this (may) be already solved in a slightly more
> complicated way. See the "Generic Reference" or "Generic Reference
> List" order arguments.
>
> Generic Reference List
> A list of reference to something.
> * A read write list of,
> * A reference, as describe in the Generic Reference System
> section.
> * The valid reference types, A list of:
> * a UInt32, read only, id of valid reference types
>
> You could then easily say that the Colonise order should take a
> reference to an object of type X?
>
> Do you think this would work? If not, could it be adapted to work? (And
> hence give a much more powerful way to say what can be selected?)
I thought of this solution... however there are a few reasons I didn't
suggest it:
a) There is currently no reference type of 'objects with type N'
- So things need to be added anyway.
b) It's a little indirect as you say ;-)
c) It would essentially deprecate the current object type, as 90% of
objects will need to be filtered. I actually think this is a killer.
If the object arg is not sufficient for the common use, it needs to be
either removed, or fixed. Just ignored, and supported in
clients/servers for no reason to be used by accident occasionally is
silly.
Regards,
nash
_______________________________________________
tp-devel mailing list
[email protected]
http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
