![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: project open triggers don't work Topic Summary: Created On: 10-Nov-2006 17:13 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
The DXL manual suggests that project open triggers are valid and there is even an example (the include file is not included in the standard install though! ($DOORSHOME/lib/dxl/triggers/projOpen.dxl isn't there)). But as far as I can see the trigger never fires at all, well either that or I'm having a funny five minutes (I'm hoping I am as I had a good use for the trigger). Any one have any success with project open triggers (I'm using DOORS 8.1)
I've checked that the dxl is successfully installed and it is there stored against the database Neihther of the following do anything: - string dxlCode = "print \"dxl documentation sucks\"" Trigger t = trigger("ProjTrig",project, pre, open, 10, dxlCode) or string dxlCode = "print \"dxl documentation sucks\"" Trigger t = trigger("ProjTrig",project->all, pre, open, 10, dxlCode) ------------------------- Regards, Richard Good |
|
![]() |
|
![]() |
|
Project Open triggers are a residual artifact from DOORS v4.0 where you had to log into each project separately (user and password). That doesn't make sense anymore since its all one big folder hierarchy. There seems to be some residual references in the DXL manual.
Project-Open is not a valid trigger event. Telelogic has made the decision to insure all DXL is backwards compatible: they now prefer "hardDelete" but still support "delete". That makes sense for functions that still apply, but I believe that 'backward compatible' policy should be aborted for old functionality that no longer applies: in this case you should get a DXL error when you try to create a project-open trigger; that would be better than letting your DXL run and getting some hard to decipher run-time error. Another example is this: in v5 OLE diagrams were in the Object and there exists function 'oleCut(Object)' which gets a copy of it. In v6 OLE diagrams are placed into any Text diagram. Well, trying to cut an 'the' OLE from the Object doesn't make any sense; thus I believe they should remove that function so that folks know they have to rethink their DXL. But no, they leave it in there and who knows what's happening when you use 'oleCut(Object)'. - Louie |
|
![]() |
|
![]() |
|
Can't believe it, why would you have an example of an unused defunct trigger four versions after you have removed it. I came at the help file from the index and know a little bit about triggers, so I didn't bother to read the introduction section again, where admittedly there is no mention of them. What's also galling is you can install them without error and query them, and no error is generated. For this reason half of me still believes there is a way to make it work. I think I'll put in a moan to DOORS Support.
------------------------- Regards, Richard Good |
|
![]() |
|
![]() |
|
Hi Richard,
did you created a support case for the stupid documentation of project triggers? What did they answer? I tried to use such a trigger too, but I was to impatient to wait 5 minutes ;-) Greetings Reik ------------------------- Evosoft GmbH for Siemens Industry Sector Berlin, Germany |
|
![]() |
|
![]() |
|
I created a support case, the answer was that it is truly wrong in the documentation and has to be changed in the future.
at least "Project->all" triggers do definetly NOT work
------------------------- Stefan Schuck Siemens - SN MN CC PM PO Berlin Germany Schuck.Stefan@siemens.com |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
project open triggers don't work
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.