What on earth is that? Do you mean an example of a trigger written in Galaxy? Just view the compiled code of your map script as GUI compiles to reasonable ones.
You cannot disable and enable triggers during run time. This is because disable and enable are GUI compiler commands which govern if the respective objects will generate script or not during translation from GUI to Galaxy.
You can however turn triggers on and off. Triggers that are off will not be fired when events it is attached to occur. They can still be executed using the run trigger action however. If your problem is that you are running a trigger with the run trigger action that is off and it still works you can get around this using a conditional test to check if it really is off and only running it if it is not off. Do note that off trigger objects still do persist as an object so although they have no execution overhead they will still have memory resource overhead.
In order to help you further you will need to explain in detail the error that is happening. This includes both what you want (are expecting) to happen and what actually happens (the error). You should also post the triggers involved and everything related to them even if seemingly unimportant (as some times its the small things causing an error). As well as this you should post a map which can be used to easily and quickly reproduce the error as many difficult errors can only be found/fixed with a bit of hands on.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
What on earth is that? Do you mean an example of a trigger written in Galaxy? Just view the compiled code of your map script as GUI compiles to reasonable ones.
You cannot disable and enable triggers during run time. This is because disable and enable are GUI compiler commands which govern if the respective objects will generate script or not during translation from GUI to Galaxy.
You can however turn triggers on and off. Triggers that are off will not be fired when events it is attached to occur. They can still be executed using the run trigger action however. If your problem is that you are running a trigger with the run trigger action that is off and it still works you can get around this using a conditional test to check if it really is off and only running it if it is not off. Do note that off trigger objects still do persist as an object so although they have no execution overhead they will still have memory resource overhead.
In order to help you further you will need to explain in detail the error that is happening. This includes both what you want (are expecting) to happen and what actually happens (the error). You should also post the triggers involved and everything related to them even if seemingly unimportant (as some times its the small things causing an error). As well as this you should post a map which can be used to easily and quickly reproduce the error as many difficult errors can only be found/fixed with a bit of hands on.