![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: dynamic triggers Topic Summary: Created On: 21-Jul-2004 20:46 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Been playing with triggers and I notice that a dynamic module-close trigger defined by a DXL will persist ONLY so long as the DXL is running, and NOT as long as the module is open, as is desirable. Keeping a DXL running means opening a Dialog Box.
For example, if you define a dynamic module-close trigger to close your dialog box, the trigger exists only if the DB is open. If you close the DB the trigger is likewise removed. That's OK in that situation. Maybe that's what those b:Specific triggers are for. Thus, it would be REAL tough to write a dynamic trigger that reminds the user that something needs to be done after they close a module; such as "you have modified this module. Be sure to put its name in the NowUpdated list". - Louie |
|
![]() |
|
![]() |
|
I've actually written quite a few persisten triggers over the years but just started investigating the dynamic ones. In my example, the persistent trigger could be a pre-close-module trigger that deletes itself:
... Trigger tCurr = current ... if user confirms some warning ... then set(preConPass); delete(tCurr) ... else set(preConFail) If I really wanted to make it bullet proof, I could get the "session" of the open module and insert it into the name. The trigger would get the current trigger handle, then get the name of the trigger, then get the session from the name. If that was not the current session the trigger (the trigger was created at some other time) then it would set pass and delete itself without ceremony. - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
dynamic triggers
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.