ExecuteFunc vs TriggerExecute?

[darkbeer]

hey there,

im currently working on a system, to which i want to pass a function, so im asking, what would be better, passing the function as string and using ExecuteFunc("") or creating a new trigger and adding the function as condition and running the trigger with TriggerExecute?

The system has to be MUI
(I remember someone saying ExecuteFunc is not MUI, but im not sure)

 

[emjlr3]

id have to see the system and what is was for to give any good reasoning

 

[Uberplayer]

Every way is MUI when done right. If you can easily do it with ExecuteFunc(..), I see no reason to create useless triggers and triggers and triggers.

 

[Vexorian]

hey there,

im currently working on a system, to which i want to pass a function, so im asking, what would be better, passing the function as string and using ExecuteFunc("") or creating a new trigger and adding the function as condition and running the trigger with TriggerExecute?

The system has to be MUI
(I remember someone saying ExecuteFunc is not MUI, but im not sure)

Code doesn't magically become or stop being MUI depending on what native you pick.

TriggerExecute does exactly what ExecuteFunc does, only that it is faster and allows the optimizer to work better.

 

[darkbeer]

thx, so ill use the trigger

 

[emjlr3]

aside from that fact that you need a trigger for it to work

 

[Vexorian]

Then use .execute()