![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: trigger help Topic Summary: Created On: 21-Feb-2003 20:35 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: If I read the code correctly, the trigger must be set by each individual user who wants that feature: if I run defview.dxl only I get prompted. If so, it appears YOU have also run that DXL on these modules. If so, run the delview.dxl script so YOU don't get prompted, but it won't affect anybody else. Then maybe you can modify the script to suppress the "confirm" command, and run the new version to not bother asking and always save the view. Perhaps you also want to add a feature where it checks to insure the module is open visibly (if isVisible(current module)), so it doesn't save views for modules opened for other reasons. But to answer your question: No, you cannot suppress individual triggers, although you CAN use the "-T" statment in your DOORS.EXE icon, and suppress running ALL triggers for a particular session, at least if you are a DOORS admin (see chapter "Command line switches") - Louie | |
![]() |
|
Howdy,
Does anybody know how to go around a persistant trigger? Specifically - Some of the modules in my database utilize the /lib/dxl/example/defview.dxl script. Whenever these modules are then opened and subsiquently closed by DXL, I am presented with a dialog to save the view. In a nutshell, how do I get around this dialog box? As always, any help is appreciated. Thanks, Mark ------------------------- Mark Phillips mark.phillips@swri.org |
|
![]() |
|
![]() |
|
If I read the code correctly, the trigger must be set by each individual user who wants that feature: if I run defview.dxl only I get prompted. If so, it appears YOU have also run that DXL on these modules. If so, run the delview.dxl script so YOU don't get prompted, but it won't affect anybody else.
Then maybe you can modify the script to suppress the "confirm" command, and run the new version to not bother asking and always save the view. Perhaps you also want to add a feature where it checks to insure the module is open visibly (if isVisible(current module)), so it doesn't save views for modules opened for other reasons. But to answer your question: No, you cannot suppress individual triggers, although you CAN use the "-T" statment in your DOORS.EXE icon, and suppress running ALL triggers for a particular session, at least if you are a DOORS admin (see chapter "Command line switches") - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
trigger help
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.