I noticed today that some of the Blizzard functions/actions/conditions/events seem to make use of parameters in a way that users (or myself at least) are un able to duplicate.
'basic type' parameters (As apposed to preset<Preset Name> parameters) seem to allow selection from a subset of presets sharing the same type (at least when blizzard uses them).
Take for example... Built-In->Unit->Basic->Unit Enters/Leaves Point
This event has a 'Unit' parameter that allows selection of the 'Any Unit' preset as well regular selection of 'units' (i.e. from last created unit or a variable of type unit). Whenever I make a 'Unit' type Parameter in an function/action/condition/event it has an empty preset list (and though it does inherit the default preset value of 'No Unit' this is not selectable from the preset list like 'Any Unit' is in Blizzards parameter.
The only way I could find to duplicate this was to ctrl+c the parameter and paste it into my condition. The problem with this is I would like to be able to select the 'No Unit' preset as well as the 'Any Unit' so that I can make a comparator to compare a fixed unit variable with a given unit/'No Unit'/'Any Unit' value.
There is an obvious workaround to get the missing 'No Unit' preset (simply go Not->My Condition('Any Unit'). Though there are many other applications where having a basic type preset with a parameter list would be very useful. If anyone has found a solution/knows what I have overlooked please tell me, its driving me nuts!
When I need no unit, I just do custom script and type null. The presets for any unit and no unit both show up in galaxy script as null, so if you need either of them, you should be able to write null.
When I need no unit, I just do custom script and type null. The presets for any unit and no unit both show up in galaxy script as null, so if you need either of them, you should be able to write null.
Yeah, I saw that myself, though how does it specify the difference between null wanting 'Any Unit' and null wanting 'No Unit' (or !'Any Unit' as you could also call it)...
As well... as I said with the unit problem there are easy workarounds but in some other cases being able to seed your parameter with a list of presets (while retaining the abbility to select from the basic type variables/values/functions) would be very time saving!
I noticed today that some of the Blizzard functions/actions/conditions/events seem to make use of parameters in a way that users (or myself at least) are un able to duplicate.
'basic type' parameters (As apposed to preset<Preset Name> parameters) seem to allow selection from a subset of presets sharing the same type (at least when blizzard uses them).
Take for example... Built-In->Unit->Basic->Unit Enters/Leaves Point
This event has a 'Unit' parameter that allows selection of the 'Any Unit' preset as well regular selection of 'units' (i.e. from last created unit or a variable of type unit). Whenever I make a 'Unit' type Parameter in an function/action/condition/event it has an empty preset list (and though it does inherit the default preset value of 'No Unit' this is not selectable from the preset list like 'Any Unit' is in Blizzards parameter.
The only way I could find to duplicate this was to ctrl+c the parameter and paste it into my condition. The problem with this is I would like to be able to select the 'No Unit' preset as well as the 'Any Unit' so that I can make a comparator to compare a fixed unit variable with a given unit/'No Unit'/'Any Unit' value.
There is an obvious workaround to get the missing 'No Unit' preset (simply go Not->My Condition('Any Unit'). Though there are many other applications where having a basic type preset with a parameter list would be very useful. If anyone has found a solution/knows what I have overlooked please tell me, its driving me nuts!
@UmbraLamina: Go
When I need no unit, I just do custom script and type null. The presets for any unit and no unit both show up in galaxy script as null, so if you need either of them, you should be able to write null.
Yeah, I saw that myself, though how does it specify the difference between null wanting 'Any Unit' and null wanting 'No Unit' (or !'Any Unit' as you could also call it)...
As well... as I said with the unit problem there are easy workarounds but in some other cases being able to seed your parameter with a list of presets (while retaining the abbility to select from the basic type variables/values/functions) would be very time saving!
@UmbraLamina: Go
I assume there is not many times if any where no unit and any unit conflict, so I assume they are just different names for the same thing.
I think the preset is an issue that will be fixed in release.