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: Post module open trigger
Topic Summary:
Created On: 23-Apr-2007 21:01
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.
 23-Apr-2007 21:01
User is offline View Users Profile Print this message


David Ehlers

Posts: 10
Joined: 23-Mar-2007

OK, here's my idea... I'd like a message box to open when I open a specific view in a specific module. It's a requirements verification module, so I'd like the message box to display the cumulative PASS, FAIL and UNTESTED counts as stored in the module. Oh, and the counting must obey a filter of my choosing. This is newbie trigger and dialog box stuff. I see some interesting DB stuff on the forum but I can't figure out the trigger issue. Any tips/references/examples?

Thanks.

<> David
Report this to a Moderator Report this to a Moderator
 24-Apr-2007 13:04
User is offline View Users Profile Print this message


Tony Goodman

Posts: 1098
Joined: 12-Sep-2002

You can define a persistent trigger in the current module as follows:

trigger("yourTriggerName", module, post, open, 5, "#include <YourCode.dxl>")

After a module opens, the trigger will fire and execute the DXL specified in the #include.
An example:

if (currentView(current Module) == "your vew name")
{
infoBox "Module open trigger fired ok"
}

-------------------------
Tony Goodman
http://www.smartdxl.com
Report this to a Moderator Report this to a Moderator
 24-Apr-2007 19:31
User is offline View Users Profile Print this message


Reik Schroeder

Posts: 361
Joined: 28-Jul-2003

Hi David, Hi Tony,

I would not suggest to use #include statement within trigger.
You may use it for development purposes in your private test module/database, but in productive database you have to assure that all users will have access to this included file and of course have the same version of script.

So when you are ready to run you should use something like this:
trigger("yourTriggerName", module, post, open, 5, readFile "YourCode.dxl");

Ok, that was sth. about triggers
Now to your described problem ... you want the trigger to fire on change of view - that may be much more complicted.
Did not found a practicable solution to this problem
Sorry.

Greetings
Reik

-------------------------
Evosoft GmbH
for Siemens Industry Sector


Berlin, Germany
Report this to a Moderator Report this to a Moderator
 24-Apr-2007 23:27
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Reik is correct. Use the readfile command, not the #include one, otherwise other folks will get errors since they don't have access to your files.

No, there is no such change-view trigger.

But your post-module-open trigger can display the dialog. The dialog can look at the current filtering. It can also have a refresh button on it which you can use to command a refresh, perhaps after loading some other view or applying some filter manually.

Triggers are tricky. I'd first get the dialog box part working; THEN hurl yourself over the cliff...

- Louie
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.