> This means that the object selection order parameter structure will look
> like,
> Object - An object's ID number.
> * a UInt32, read write, objects id
> * a list of, read only,
> * a UInt32, the valid types of objects
Yep... Empty list means all types correct?
<Lists>
> To make a list which can only have one item selected, a "total maximum"
> argument will be added (got no idea why we left that off the first
> time).
Silly question... is it worth adding a 'weight' field and changing the
total maximum to be a total weighted maximum?
So that sum of each items #selected * weight < total weighted maximum.
I'm just thinking this takes the normal case for building stuff really
nicely... So building ships and stuff can be done automatically in the
client in an easy way?
Also trading games with different cargo units can work with the list
easily too.
Obviously doesn't solve all cases, but it works instantly with RFTS and
trading games.
Otherwise... all good.
> This means that the list order parameter structure will look like,
Updated version by nash:
> List - A list in which one or more items can be selected
> The possible selections,
* A list of:
* a UInt32, read only, id of what can be selected
* a String, read only, String Name of can be
selected
* a SInt32, read only, maximum number of can to be
selected, -1 means no limit
* an UInt32, read only, weighting.
0 means doesn't count to limit
* a GRS list, read only, What this item refers too
* a SInt32, read only, the total weighted maximum number of things
which can be selected, -1 means no limit.
The selection, A list of:
* a UInt32, read write, id of the selection
* a UInt32, read write, number of the selection
Regards,
nash
_______________________________________________
tp-devel mailing list
[email protected]
http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
