Thanks for the feedback, General and HateR
Anyway, I just dropped here to give hails because I was just about to start doing pretty much the same thing as these functions of yours do, gladly I checked the Ed Depot first
That's what they're for!
I was going to suggest the exact same thing. One other example of why you would want to do this would be if you are using these functions in an addon. Obviously, you wouldn't want the addon's variables to over-write any mission variables
No, in you can have two identical sets of the functions, one in the addon, one in the mission, and they will complement each other perfectly. You can simply have this:
["Mission Variables","MissionVar1",player] call SetProperty
["Addon Variables","MissionVar1", leader player] call SetProperty
which will work fine. Of course, nothing is stopping you from having different names for your global array.
Obviously, you could just edit the functions and change the var names yourself, but that is beside the point...
Well, no, that is precisely the point! Only a few quick edits to rename 'Properties' for each func, and you'd be sorted. That is quite alot easier than the alternative, supplying your Global Array name as an argument. I'd like to keep the number of arguments as small as possible; it makes for a tidier, more compact 'call' plus there's less to remember! And, you'd be essentially doing the same thing each time:
[object,"Property",value,"MY GLOBAL ARRAY"] call SetProperty
However, if it looks like having separate global arrays is a better idea becuase of what HateR said about array sizes getting too large, I will happily incorporate this argument in as well.
RE: tags. So I should make it 'FRG_properties'? I think I registered FRG a while back... have to check that...