![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Getting module details in pre-triggered DXL code Topic Summary: Created On: 31-Jan-2005 12:29 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: I don't think the DOORS explorer method will work since it will give false info if you open a module by some other means, such as following a link. If your pre-open trigger is stored in each module, then you can use the "stored" command to figure out the base name of the module. In any case, you can't find the triggers therein unless you open the module anyway. Consider a post-open-module trigger that closes the module if things don't go that well. Perhaps making it a priority 1 Trigger will cause it to run completely before other triggers fire (I don't know). If your goal is to find and destroy hostile triggers then you can use the "-T" command line switch to do so, but I think you need to be a DOORS admin for that to work: put this in the 'Target' of some DOORS icon: "...doors.exe -T". Then write code seaching for triggers. If your goal is to find and display all triggers that WILL fire when you open a module ... good luck. You'll need to look for triggers in the Module, the housing Project, and in the Database. Good luck parsing trigger assembly code to figure out which ones apply to your module. Dumping that stuff and letting someone look it over looks like the "best" choice, such as it is. - Louie | |
![]() |
|
Hi,
I need to get details of a module in pre-triggered dxl code. This includes the name of the module being opened and the name of triggers contained within it. I cant use the normal m=current affair as the module has not been effectively opened yet. One possible solution is to get the name from the module highlighted in the main DOORS interface. Any ideas how to solve this one? |
|
![]() |
|
![]() |
|
To get the currently highlighted module in the DOORS explorer, you could try the following code. I've used the type ModName_, as I don't think the module will be open yet, since you'll be using it a pre-open trigger.
Item i = getSelectedItem ModName_ modHandle = null if (type(i) == "Formal") { modHandle = module(i) } if (!null modHandle) { // get info about the module string modName = name(modHandle) string fullModName = fullName(modHandle) } Edited: 31-Jan-2005 at 13:51 by Antonio Norkus |
|
![]() |
|
![]() |
|
I don't think the DOORS explorer method will work since it will give false info if you open a module by some other means, such as following a link. If your pre-open trigger is stored in each module, then you can use the "stored" command to figure out the base name of the module. In any case, you can't find the triggers therein unless you open the module anyway.
Consider a post-open-module trigger that closes the module if things don't go that well. Perhaps making it a priority 1 Trigger will cause it to run completely before other triggers fire (I don't know). If your goal is to find and destroy hostile triggers then you can use the "-T" command line switch to do so, but I think you need to be a DOORS admin for that to work: put this in the 'Target' of some DOORS icon: "...doors.exe -T". Then write code seaching for triggers. If your goal is to find and display all triggers that WILL fire when you open a module ... good luck. You'll need to look for triggers in the Module, the housing Project, and in the Database. Good luck parsing trigger assembly code to figure out which ones apply to your module. Dumping that stuff and letting someone look it over looks like the "best" choice, such as it is. - Louie |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.