![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Closing a baseline closes module trigger Topic Summary: Created On: 13-Aug-2007 12:58 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi all,
in a dialog box framework, I have defined a dynamic object sync trigger on the current module. Now, when I am reading and closing a baseline of the current module, the trigger gets deleted. Is there a way to prevent this, i.e. to only delete the trigger when the current module is closed? Regards, Peter |
|
![]() |
|
![]() |
|
Use the isbaseline function within the trigger code ie do something if the module is the current version and nothing if it is not
------------------------- Regards, Richard Good |
|
![]() |
|
![]() |
|
Thanks for answering.
The problem is not with the trigger code, even if the trigger code is empty, the problem persists. My problem is, that the dynamic trigger is deleted when the baseline is closed. As far as I know, this is done via an automatically created built-in trigger, which fires when the baseline is closed. Now, the latter I can't modify, as it is created automatically by DOORS/DXL. Regards, Peter |
|
![]() |
|
![]() |
|
I wonder if there is some confusion about dynamic triggers vs. persistent. If your trigger is "dynamic" in the sense that the DXL manual talks about, then it is supposed to go away. To have a trigger stay attached to a module you use a "persistent" one; a dynamic trigger is "Not stored; persists only for the loaded lifetime of the project or module that defines it."
I haven't used dynamic ones myself, but we have a global post-open trigger (persistent) on our DB. Chris |
|
![]() |
|
![]() |
|
I'm guessing but am fairly confident the following is true: When you define a Dyanmic trigger DOORS creates a 'Build In' trigger whose job it appears to be to remove the Dynamic trigger when its context is removed; i.e. remove the Dynamic trigger when the module closes. I notice that module-level triggers fire when you open a baseline and that its difficult for the trigger to recognize that its a baseline opening and not the current version. I conclude that the Built In trigger is seeing the baseline close, doesn't realize its a baseline, and is removing the Dynamic trigger.
Sounds like a bug to me. Don't know what to do about it, other than another trigger that stops baselines from closing if this Dynamic trigger is installed. - Louie |
|
![]() |
|
![]() |
|
@Chris: I want to use dynamic triggers, as the goal is to update a dialog box when the user selects a new object. There is no point in creating a persistent trigger for this, as it only makes sense for the current module and with the dialog box open. And yes, it is supposed to go away, but only with the current baseline for which it was created, and not with baselines of the same module, opened later.
@Louie: I think you are pretty right. At least I observed those build-in triggers, too, which are automatically created whenever a new dynamic trigger is created. Given a previous thread in this forum, I can understand that those build-in triggers have difficulties distinguishing baselines from current modules. As for preventing to close the baselines: I'd like to avoid this, as the baselines consume quite a bit of memory. In the meantime I just accepted the unavoidable and changed the code such as to re-deploy the trigger after I looped through the baselines. It works, and I just have to make sure that the trigger is really deleted, just in case Telelogic solves this bug in the future. Thanks for answering, Peter |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Closing a baseline closes module trigger
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.