![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Running DXL from a menu Topic Summary: Created On: 15-Nov-2004 18:25 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: wrt The point about them sometimes not being present, the user file menu only gets set up at opening the module. So if you add a file while the module is open it wont appear. Close and reopen the module and there it is. | |
![]() |
|
I am trying to run dxl scripts from the User menu (available when a module is open).
When I put the dxl files in ...\lib\dxl\addins\user\ (on my local machine) they sometimes show up and sometimes they don't. Also I would like to be able to put them in the same location on the server, so the users can use them. How do I get DOORS to look at the server location instead of my local machine, and how do I make sure the script will show up as a menu item once the file is copied to the proper location. We are using DOORS 6.0 SR1 build 60202 Thanks, Al Lione albert.lione@ngc.com |
|
![]() |
|
![]() |
|
[1] Deployed scripts must be formatted as follows:
First line is a comment and shortly thereafter there is a comment block. Example: // MyPrivateScript.dxl - Find last modified Objects in the current module const string NameAttr = "Last Modified On" /* MyPrivateScript.dxl finds the 5 last modified objects in the current module and filter for them. There is no dialog, it just does it. */ Yaddy Yad. [2] Once deployed, the first line appears in the >>Tools>>Dxl Library list, and the comment block appears therein when you click on a particular script. Those two comments are great places to document what the script actually does. [3] If you edit the "*.idx" file (in this case ../Addins/User/User.idx) you can put the script name and the blurb that will be seen in the menu. Failing to insert an appropriate line in the IDX will result in files showing only the script name ..err.. script's file name, in this case "MyPrivateDXL". My *.idx lines look like this: MyPrivateScript _ _ MyPrivateScript: Find Last Modified Objects The first word is the name of the *.dxl file, the last few are the blurb that appears in the menu. The two underscores are for shortcut keys (such as cntr-shft-A) ,and I don't use them. [4] The /addins folder is automatically part of your addins path, and so you always get its subfolder User menu. You can suppress that menu by renaming folder "user" to "userold", which I recommend for folks who don't deploy there (takes that User menu off your Module windows). [5] You can deploy on the Server but that requires updating everyone's registry entries to create new "addins" environment variable. Search for "deploy" for other posts about that. - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Running DXL from a menu
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.