![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Trigger related to the open event Topic Summary: Created On: 27-Oct-2006 13:42 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hello all,
I implemented a persistent trigger on module level invoked during the open event. The problem is the trigger runs not only when the user opens the module. It also runs when the module is copied from one folder to other one or when the user changes the edit mode from "read" to "exclusive edit". Is it possible to avoid executing the code in these cases? Regards Darius Dolnik |
|
![]() |
|
![]() |
|
I don't think it is possible to stop the trigger running under those circumstances, but it is definately possible to put logic into the trigger such that it only does what ever you want it to do when the module is opened for exclusive edit - visible. You can also detect if the module is already open read only, simply wrap the logic around the trigger, such that if the conditions aren't met then the trigger does nothing.
------------------------- Regards, Richard Good |
|
![]() |
|
![]() |
|
I expound Good's response. Inside the trigger code you can do something like this:
Module mCurr = current if (!isVisible(mCurr)) halt if (!isEdit(mCurr)) halt The nature of changing the edit mode of a module requires the module to be re-opened if the mode is increased; when going from Read to Edit you need to go back to the server and retrieve the latest information, which could reasonably have changed after you originally opened it Read. Share to Edit likewise reopens the module. Notice the trigger doesn't fire when downgrading from Edit to Read. Didn't know the module is opened in order to move it. - Louie |
|
![]() |
Telelogic DOORS
» General Discussion
»
Trigger related to the open event
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.