![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
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 |
![]() |
![]()
|
![]() 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. | |
![]() |
|
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 |
|
![]() |
|
![]() |
|
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 |
|
![]() |
|
![]() |
|
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 |
|
![]() |
|
![]() |
|
Thanks, I will give that a go.
![]() |
|
![]() |
|
![]() |
|
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. |
|
![]() |
|
![]() |
|
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. |
|
![]() |
|
![]() |
|
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.
|
|
![]() |
|
![]() |
|
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 |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.