![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Can I find method of module open from within triggered code? Topic Summary: From code run via a module open trigger, can I determine if a module was opened via Explorer or via link navigation? Created On: 4-Mar-2007 16:50 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
My application requires execution of one set of code if module was opened via the DOORS Explorer and execution of a different set of code if the module was opened via navigating a link from an object in another module.
From code run via a module pre or post open trigger, can I determine if the module (to which the trigger is attached) was opened via Explorer or via link navigation? |
|
![]() |
|
![]() |
|
I edit this message to say what I was thinking -- you could use isVisible, isEdit, isShared etc to make some deductions about the state that may be accurate enough to satisfy your needs.
Edited: 5-Mar-2007 at 17:10 by ron lewis |
|
![]() |
|
![]() |
|
Ron he's talking about opening a module by clicking on a link from another. That isVisible() check wouldn't work because when you click a link, it opens the module to be viewed, not in the background. So whether opened from the DOORS explorer or from clicking on a link, that isVisible() check would always return true. ------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
Hi all, I have the same problem, and I don't find any propertie of Module or Trigger to determine whether the module was opened directly from DOORS Explorer or through link navigation. One way to solve this issue would be to identify the link which fired the trigger. Edited: 1-Jun-2007 at 12:37 by Frederic GIL |
|
![]() |
|
![]() |
|
Hi Bob, Hi Frederic,
AFAIK you can not determine wich event triggered the opening of module. If you explain wherefore you need to distinguish between the two possebilities, this community may help you to find another option for handling that issue?! ![]() I can not really imagine wherefore someone could need this. It makes much sense to know something about the module state as Ron already mentioned. Have a nice weekend @all, Greetings Reik ------------------------- Evosoft GmbH for Siemens Industry Sector Berlin, Germany |
|
![]() |
|
![]() |
|
> I can not really imagine wherefore someone could need this. In fact, we need this ! |
|
![]() |
|
![]() |
|
You might be able to modify each client dxl software such that the dxl scripts call your dialog box.
Question to be answered is, is ever way that open a module thru the gui implemented in unencrypted dxl? |
|
![]() |
|
![]() |
|
There are three ways to open a module from the GUI.
1. From the explorer file menu. 2. From the explorer toolbar 3. From the explorer listview popup menu. These options all call one of the functions openReadOnly, openShare or openEdit. These functions are defined in baseWindowCallbacks.inc, which is encrypted so you can't change them. You can however change baseWindowMenu.inc which contains the calls to these functions. Wrap, or replace, the calls to these in your own function or use a global togther with a module open trigger. Set the global to record that the module open request came from the GUI, inspect the global (and reset it!) in the trigger. Unfortunatley this approach requires installing DXL on all the clients which I know it not easy in most organisations. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Hi Richard,
what do you think about to set the default open mode for formal modules to read only. So when user follows a link (s)he will open the away module in read only mode. When user explicitely opens the module in shareable/exclusive mode your trigger will see it ![]() So in trigger code you would need only to check for open mode of module to be not read only by using isRead function.... May be that this is an easy to implement option for you ![]() Greetings Reik ------------------------- Evosoft GmbH for Siemens Industry Sector Berlin, Germany |
|
![]() |
|
![]() |
|
Some aditional information can be found in Doors manual in chapter "Summary of command line switches"
The interesting option is defopenlinkmode quote: Greetings Reik ------------------------- Evosoft GmbH for Siemens Industry Sector Berlin, Germany |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.