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 to recognize baselines
Topic Summary:
Created On: 16-Nov-2007 21:34
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.
 16-Nov-2007 21:34
User is offline View Users Profile Print this message


Scott Covington

Posts: 17
Joined: 29-Nov-2004

I'm trying to create a trigger that only pops up a message when the current version of a module is opened, but it pops the message when the baselines open too.

I've simplified it down to this:

Trigger t1 = trigger("openNotice", project->all->module->formal->all, post, open, 10, "Trigger t = current ; ack versionString( moduleVersion( current Module ) ) ")

but I'm stumped. If I execute the ack line in the baseline, it gives me the baseline information. However in the trigger it doesn't.

It appears that the "current Module" reference doesn't work in this context like I expected. Does anyone know how to make this work?
Report this to a Moderator Report this to a Moderator
 16-Nov-2007 23:46
User is offline View Users Profile Print this message


David Pechacek

Posts: 674
Joined: 5-Dec-2006

Use this function.

bool isBaseline(ModuleVersion modver| Module m)

-------------------------
David Pechacek
AAI Services Textron
dpechacek@sc-aaicorp.com
David.Pechacek@gmail.com
Report this to a Moderator Report this to a Moderator
 19-Nov-2007 15:41
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

You need to get the Module handle of the module whose open event fires the trigger. That's different than getting the Module handle of the module that stores the trigger.

The attached seems to work.

I'm shocked to discover that the trigger fires before the module has had a chance to become 'visible'. The commented-out line inside the trigger always displays 'Visible false' even for baselines that are open, but when opening a module from the Explorer, it DOES wait for it to become visible before firing.

Thus, as far as I know right now, checking for 'isVisible' inside a module-trigger only works for the current version, won't work for opening baselines.

- Louie

Edited: 19-Nov-2007 at 15:42 by Louie Landale
Report this to a Moderator Report this to a Moderator
 25-Feb-2008 21:23
User is offline View Users Profile Print this message


Thomas Young

Posts: 20
Joined: 12-Apr-2005

Louie,
Just wanted you to know I had the same problem, and your code (small chunk from) solved it. Thanks for all your valuable forum contributions.
Tom Y.
Report this to a Moderator Report this to a Moderator
 3-Oct-2008 18:31
User is offline View Users Profile Print this message


Uma Unnikrishnan

Posts: 14
Joined: 8-Jul-2008

Thank you Louie, I too was facing the same problem...your code helped.

~uma
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 2 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 2 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.