Markers and JIP persistancy...with CBA_fnc_setMarkerPersistant

[CarlosTex]

Just for info:

I couldn't not make your function to work. I set it up on init.sqf like this:

if (isServer) then {
   // Setup eventHandler
   ["TEX_markers", 
	{ 
	_marker = _this select 0; //String
	_pos = _this select 1; //Array
	_shape = _this select 2; //String
	_type = _this select 3; //String
	_size = _this select 4; //Array 
	_color = _this select 5; //String
	_mkr = createMarker [_marker, _pos];
	_marker setMarkerShape _shape;
	_marker setMarkerSize _size;
	_marker setMarkerColor _color;
	}] call CBA_fnc_addEventHandler; //EventHandler	
	
   // Helper function
   TEX_fnc_createMarker = { ["TEX_markers", _this] call CBA_fnc_localEvent }; // no need to broadcast, we're already on the server
} else {
   // Helper function
   TEX_fnc_createMarker = { ["TEX_markers", _this] call CBA_fnc_globalEvent }; // broadcast to execute on server
};


// To create a marker:
["MarkerOne", (getmarkerpos "mkrpos"), "icon", "mil_warning", [0.5,0.5], "ColorGreen"] call TEX_fnc_createMarker;

No errors, no nothing, diag_log shows nothing wrong in RPT but marker is never created. It would be nice to have this function working but i won't cry for it.

[Sickboy]

Does the "mkrpos" marker exist, and diag_log

(getmarkerpos "mkrpos") shows correct value?

[CarlosTex]

Yes it is editor place. And diag_log (getmarkerpos "mkrpos") returns as well.

[Sickboy]

I suppose the main problem is that you do not use

_marker setMarkerType _type;

[CarlosTex]

OMG!!!!

[Sickboy]

Haha, love the smiley No worries, happens to us all :P

[CarlosTex]

BTW, how beneficial do you consider if i decide to precompile it, since i'm probably gonna call it quite a few times during the mission?

[Sickboy]

BTW, how beneficial do you consider if i decide to precompile it, since i'm probably gonna call it quite a few times during the mission?

It already is precompiled.

---------- Post added at 12:21 ---------- Previous post was at 12:15 ----------

The diff is in:

A) Not precompiled
Init: Nothing
Call:

[someParam, someParam2] call compile preProcessFileLineNumbers "functionName.sqf";

vs

B) Precompiled
Init:

TEX_functionName = { .... function content ... };

Which could also have been (no real difference other than directory structure):

TEX_functionName = compile preProcessFileLineNumbers "functionName.sqf"

Call:

[someParam, someParam2] call TEX_functionName;

[CarlosTex]

OK, i wrote the function in a separate script called "fn_createMarkers.sqf".

So in the init.sqf i have:

call compile preProcessFileLineNumbers "functions\fn_createMarkers.sqf".

So this would be getting the same result because it is already precompiled?:

execVM "functions\fn_createMarkers.sqf"

I thought that preCompiling meant something like when you write a program in C# language and then compile it with GCC, ICC or Open64 compilers makes it faster because you're not running raw data (and obviously compiler also translates it into machine language). (Probably now you'll get that i understand 0 about programming).

So basically doing:

global or local variable = {code here};

already precompiles it?


EDIT: BTW when i tested my mission precompiling the function in the init.sqf and creating the markers using the function everything is working fine. But with your explanation i understand now that i also could have execVM "functions\fn_CreateMarkers.sqf" and it would be the same.

So what's the point of having the command if you can preCompile in the scripts instead?

[Sickboy]

Nope you misunderstood me.

As said you already precompiled the function from the beginning by specifying it as TEX_name = { ... }, there is nothing more you need to do.
TEX_name = { ... }; comes down to the same as putting the code in a sqf and then using TEX_name = compile preProcessFileLineNumbers "file.sqf";

Especially don't use execVM if you are going to use it over and over, besides that it is to run scripts, and not to call functions that return anything.