How to enable a disabled local trigger?

[Geshishouhu]

If I disable a local trigger, how should I enable it afterwards? An answer with a short example is more welcomed. Thanks guys.

 

[Rheiko]

what do you mean by local trigger?
this?:

• Trigger - Turn off this trigger
• Trigger - Turn on this trigger

 

[chobibo]

Don't use a local trigger if you want to use it that way. Use a global variable instead.

 

[Rheiko]

oh lol, i thought..
yeah as chobibo said

 

[Geshishouhu]

Don't use a local trigger if you want to use it that way. Use a global variable instead.

All right, thnx, chobibo.

oh lol, i thought..
yeah as chobibo said

It's like

local trigger t=CreateTrigger()

 

[Rheiko]

i know

 

[nhocklanhox6]

You can disable and enable local trigger by do it in the same function..haha (Just kidding ^^)

 

[Geshishouhu]

i know

Sorry for the confusing question. +Rep

You can disable and enable local trigger by do it in the same function..haha (Just kidding ^^)

LOL

 

[Malhorne]

Yes but it is ...
Useless ?

There is often way to do without turning on/off triggers
Like adding conditions or something like that.

 

[chobibo]

That depends, sometimes you want to disable events.

 

[FUJI]

"If I disable a local trigger, how should I enable it afterwards? An answer with a short example is more welcomed. Thanks guys."
Maybe this:

function Trig_Sentinel_Forests_Conditions takes nothing returns boolean
    return IsUnitType(GetEnteringUnit(), UNIT_TYPE_HERO) == true
endfunction

function Trig_Sentinel_Forests_Actions takes nothing returns nothing
    call BJDebugMsg("Off")
    call DisableTrigger( GetTriggeringTrigger() )
    call PolledWait( 5.00 )
    call BJDebugMsg("On")
    call EnableTrigger( GetTriggeringTrigger() )
endfunction

//===========================================================================
function InitTrig_Sentinel_Forests takes nothing returns nothing
    local trigger gg_trg_Sentinel_Forests = CreateTrigger(  )
    call TriggerRegisterEnterRectSimple( gg_trg_Sentinel_Forests, gg_rct_Sentinel_Forest )
    call TriggerAddCondition( gg_trg_Sentinel_Forests, Condition( function Trig_Sentinel_Forests_Conditions ) )
    call TriggerAddAction( gg_trg_Sentinel_Forests, function Trig_Sentinel_Forests_Actions )
endfunction

 

[Malhorne]

Don't forget to null the trigger local handle.

 

[TriggerHappy]

Don't forget to null the trigger local handle.

IIRC that's not necessary.

I think the reason being that the trigger isn't destroyed or something..

 

[Malhorne]

Yes but there is still some memory that are taken to store it ....
It is not really needed but it is better in term of convention xD

 

[FUJI]

Don't forget to null the trigger local handle.

Yeah I forgot :/, but it is just a example code and it is focused in the function actions .

 

[TriggerHappy]

http://www.wc3c.net/showpost.php?p=1080654&postcount=3

 

[Malhorne]

http://www.hiveworkshop.com/forums/world-editor-help-zone-98/nullify-triggers-locals-238820/
I asked it and we told me to nullify it.

 

[PurgeandFire]

@Malhorne:

As DSG said:

Yes if you plan to destroy the trigger, otherwise no as the handle index can never be recycled unless the trigger is destroyed.

But most people tend to null it anyway because:
(1) It isn't bad to do so. (it isn't necessarily beneficial either)
(2) It takes too much time to determine whether you are going to permanently keep the object, and whether it is reference counted (agent) vs. a normal handle (these types do not suffer that local reference bug, e.g. texttags).

 

[Malhorne]

Yes better null it since you don't know each time what you will do and it does not matter of speed xD

 

[Geshishouhu]

"If I disable a local trigger, how should I enable it afterwards? An answer with a short example is more welcomed. Thanks guys."
Maybe this:

function Trig_Sentinel_Forests_Conditions takes nothing returns boolean
    return IsUnitType(GetEnteringUnit(), UNIT_TYPE_HERO) == true
endfunction

function Trig_Sentinel_Forests_Actions takes nothing returns nothing
    call BJDebugMsg("Off")
    call DisableTrigger( GetTriggeringTrigger() )
    call PolledWait( 5.00 )
    call BJDebugMsg("On")
    call EnableTrigger( GetTriggeringTrigger() )
endfunction

//===========================================================================
function InitTrig_Sentinel_Forests takes nothing returns nothing
    local trigger gg_trg_Sentinel_Forests = CreateTrigger(  )
    call TriggerRegisterEnterRectSimple( gg_trg_Sentinel_Forests, gg_rct_Sentinel_Forest )
    call TriggerAddCondition( gg_trg_Sentinel_Forests, Condition( function Trig_Sentinel_Forests_Conditions ) )
    call TriggerAddAction( gg_trg_Sentinel_Forests, function Trig_Sentinel_Forests_Actions )
endfunction

@Malhorne:

As DSG said:



But most people tend to null it anyway because:
(1) It isn't bad to do so. (it isn't necessarily beneficial either)
(2) It takes too much time to determine whether you are going to permanently keep the object, and whether it is reference counted (agent) vs. a normal handle (these types do not suffer that local reference bug, e.g. texttags).

Yes better null it since you don't know each time what you will do and it does not matter of speed xD

Thank you all.