![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Getting current module Topic Summary: Created On: 8-Dec-2004 12:39 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: I wondered if triggers were the solution. Thanks Tony. | |
![]() |
|
I have a dialog box which remains open, and I want it to work on the most recently opened (i.e. "current") module, yet I cannot get it to identify that module.
If my code is run from the DOORS explorer then it will return error "null Module parameter was passed into argument position 1" If it is run from with a particular module it always returns the name of that module, never the most recently opened module. So how do I get the most recently opned module? Here's my code which demonstrates the problem DB dbTest = topMost "Get Current Module" void fnTest(DB Test) { Module modCurrent = current ack name modCurrent } apply(dbTest, "GET", fnTest) show dbTest |
|
![]() |
|
![]() |
|
I struggled with this one for a while too.
DOORS loses the "current" thing when the window focus changes so you can never get current Module or current Object to return what you are after. I was interested in the current Object. My solution was to create a persistent trigger that fired on an object sync event. The trigger sets a global Object variable to the current object. Not ideal, but it works. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
I wondered if triggers were the solution.
Thanks Tony. |
|
![]() |
|
![]() |
|
After thinking "how simple", it took me a while to sort this out.
I've attached some code which could help |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Getting current module
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.