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: Modules dissapear to the back on opening
Topic Summary:
Created On: 2-Nov-2007 09:57
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.
Answer This question was answered by Jo Chandler, on Tuesday, November 6, 2007 4:45 PM

Answer:
Not to worry, I found a trigger written by someone else that was causing the problem in the first place and have fixed that instead.
 2-Nov-2007 09:57
User is offline View Users Profile Print this message


Jo Chandler

Posts: 20
Joined: 25-Oct-2007

When I open a module, it dissapears behind the main database window. This is quite annoying.
I have release 8.1, and apparently this issue has been fixed. Does anyone have a quick script that will stop this happening?
Also, how do you make a script run when a module is opened?
Thanks!
Jo
Report this to a Moderator Report this to a Moderator
 2-Nov-2007 11:44
User is offline View Users Profile Print this message


Tony Goodman

Posts: 1098
Joined: 12-Sep-2002

To make a script run when a module is opened you need to create a trigger.

There are a lot of posts about triggers and they are described in the help.

The following function is new and can be used to bring the module window to the front:
string bringToFront()
string bringToFront(Module)

This perm is mentioned in the release notes but is not in the help.

-------------------------
Tony Goodman
http://www.smartdxl.com
Report this to a Moderator Report this to a Moderator
 2-Nov-2007 13:55
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Attached find a simple trigger that will do it. For modules opened visibly it brings them to the front.

If you set 'NameUser' to the name of your user, then the trigger only works for you. If you set 'NameUser' to null "", then it will bringToFront every module opened visible for all users.

After debugging, comment out the 'infoBox' line.

If you make changes to the code, you must confirm deleting before confirming Deploying it.

I suggest you deploy this for yourself only and see how it works for a week or so, before deploying it for all users.

- Louie

Edited: 2-Nov-2007 at 13:56 by Louie Landale
Report this to a Moderator Report this to a Moderator
 6-Nov-2007 09:31
User is offline View Users Profile Print this message


Jo Chandler

Posts: 20
Joined: 25-Oct-2007

Thanks, I will give that a go.
Report this to a Moderator Report this to a Moderator
 6-Nov-2007 10:31
User is offline View Users Profile Print this message


Jo Chandler

Posts: 20
Joined: 25-Oct-2007

Hi,
I have implemented the code posted by Louie and it seems to work ok, but I don't understand how I make it run automatically every time I open a module.
Apologies if I'm being a bit daft!
Thanks.
Report this to a Moderator Report this to a Moderator
 6-Nov-2007 15:21
User is offline View Users Profile Print this message


Jo Chandler

Posts: 20
Joined: 25-Oct-2007

Maybe I should be a bit clearer...
To be able to run that bit of code, I have to open a module, then do edit dxl, then run it. What I want to do is have that bit of code running in the background somehow so that everytime I open a module, that trigger brings the module to the front. Does that make sense?
Thanks.
Report this to a Moderator Report this to a Moderator
 6-Nov-2007 16:45
User is offline View Users Profile Print this message


Jo Chandler

Posts: 20
Joined: 25-Oct-2007

Answer Answer
Not to worry, I found a trigger written by someone else that was causing the problem in the first place and have fixed that instead.
Report this to a Moderator Report this to a Moderator
 6-Nov-2007 19:12
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

If you look closely at the 'trigger' command, you see that the level is 'project->all->module->all". The 'project->all' part means the trigger will be stored in the database. The 'module->all' part means the trigger applies to every module. That is, you run the script from the database explorer (not any particular module), and it deploys the trigger in the database and then runs 'in the background' from that time on. I'm sure whoever runs the script needs RMCD access to the database root folder.

Curious there was some other trigger that moved the module window to the rear. Just as an acedemic excercise and you don't want to delete that trigger, then my trigger should be given a very low priority (meaning a high 'Priority' value), to make sure this module-level trigger runs AFTER the other one. i.e. change the '5' in the delete and the trigger lines to something big, perhaps '100'.

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