Command-line "addins" switches override registry?

My company now has DOORS 9.3 running on Windows and now the addins information is stored in the registry now (in DOORS 8 it was a command line switch associated with the DOORS icon).

From my tests, if I modify the icon I use to launch DOORS so that it adds a "-addins" switch for my own scripts, then the scripts I add appear but I loose the standard company-defined scripts from the registry-defined addins value. So my only alternative is to copy the registry value to my icon, but that leads to a possibility of my icon getting out of date if the company path is changed and I don't notice (albeit that would not be a common thing).

Am I correct? Or is there a way to have the registry-defined addins and command line-defined addins BOTH appear?

Thanks in advance.
strathglass - Fri Mar 25 07:42:52 EDT 2011

Re: Command-line "addins" switches override registry?
llandale - Fri Mar 25 14:28:03 EDT 2011

Yup, it does that; you cannot get around it with "addins" variables.

But Wait! Never done it, but you can probably put this command
createAddinPathMenus("d:/MyAddins/Addins")
in some valid *.dxl file here:
"lib/dxl/config/formalfiles"

and I suspect you'll get your addins.

  • Louie

Re: Command-line "addins" switches override registry?
strathglass - Mon Mar 28 07:36:55 EDT 2011

llandale - Fri Mar 25 14:28:03 EDT 2011
Yup, it does that; you cannot get around it with "addins" variables.

But Wait! Never done it, but you can probably put this command
createAddinPathMenus("d:/MyAddins/Addins")
in some valid *.dxl file here:
"lib/dxl/config/formalfiles"

and I suspect you'll get your addins.

  • Louie

Thanks for the idea Louie.
I think for now I will just hard code into the "-a ..." option value for my scripts and append also the default value for the company scripts - using the registry value (since it will not be changed often, if at all).

Regards,
strathglass.

Re: Command-line "addins" switches override registry?
rmoskwa - Mon Mar 28 12:18:22 EDT 2011

Wouldn't you keep your local DXLs in something like
C:\Program Files\IBM\Rational\DOORS\9.2\lib\dxl\addins\user
where user.idx, and the contents of this user folder, define what appears in the DOORS menu bar for any formal module.
This is how DOORS presently creates the user menu item (by default) just before the Help menu item for your formal modules.

You would then create a company addins folder "somewhere on your network". You would point DOORS to it either by the registery or command-line switch in the shortcut DOORS icon. Something like CompanyUser.idx, and the contents of this CompanyUser folder, would define what appears in the DOORS menu bar, perhaps the name Company User for its associated menu item for any formal module.

I do this to separate my DXL experiments from the Company DXLs that are OK for others to use.

PS don't forget about that pesky CompanyUser.hlp file that must accompany the CompanyUser.idx file.

Re: Command-line "addins" switches override registry?
strathglass - Tue Mar 29 06:44:51 EDT 2011

rmoskwa - Mon Mar 28 12:18:22 EDT 2011
Wouldn't you keep your local DXLs in something like
C:\Program Files\IBM\Rational\DOORS\9.2\lib\dxl\addins\user
where user.idx, and the contents of this user folder, define what appears in the DOORS menu bar for any formal module.
This is how DOORS presently creates the user menu item (by default) just before the Help menu item for your formal modules.

You would then create a company addins folder "somewhere on your network". You would point DOORS to it either by the registery or command-line switch in the shortcut DOORS icon. Something like CompanyUser.idx, and the contents of this CompanyUser folder, would define what appears in the DOORS menu bar, perhaps the name Company User for its associated menu item for any formal module.

I do this to separate my DXL experiments from the Company DXLs that are OK for others to use.

PS don't forget about that pesky CompanyUser.hlp file that must accompany the CompanyUser.idx file.

That would work except I want my own scripts to be on the network since I want to run them from the PCs in the meeting rooms we have. :(

-strathglass

Re: Command-line "addins" switches override registry?
SystemAdmin - Thu Mar 22 09:40:38 EDT 2012

hello,

when using the -a in the short it points to my custom "addins" folder but it also bring in the functionality from the default location is there a way of forcing it to only analysis my custom "addins" folder?

-Jim

Re: Command-line "addins" switches override registry?
llandale - Thu Mar 22 12:57:04 EDT 2012

SystemAdmin - Thu Mar 22 09:40:38 EDT 2012
hello,

when using the -a in the short it points to my custom "addins" folder but it also bring in the functionality from the default location is there a way of forcing it to only analysis my custom "addins" folder?

-Jim

It always looks here:
  • C:\Program Files\IBM\Rational\DOORS\9.3\lib\dxl\addins
  • C:\Program Files\IBM\Rational\DOORS\9.3\lib\dxl\config\formalFiles
..err.. I mean here:
  • <DoorsHome>\lib\dxl\addins
  • <DoorsHome>\lib\dxl\config\formalFiles

I don't recommend it, but perhaps you can trick it with a pre-module-open trigger that changes "doorshome", and a post-module-open trigger that changes it back.

-Louie

The addins in the registry are ignored when there is a command switch.