Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
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
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 27-Oct-2006 13:42
User is offline View Users Profile Print this message


Darius Dolnik

Posts: 16
Joined: 13-Jul-2004

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
Report this to a Moderator Report this to a Moderator
 27-Oct-2006 14:49
User is offline View Users Profile Print this message


Richard Good

Posts: 152
Joined: 22-Mar-2005

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
Report this to a Moderator Report this to a Moderator
 27-Oct-2006 19:37
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

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
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.