![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Custom CP Scripting Topic Summary: Using custom CP scripts in 8.1 Created On: 26-Sep-2006 19:08 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
We have scripting set up so that our own code will execute before and after the user is presented with the standard Telelogic CP dialog boxes. Basically, we've modified lib/dxl/standard/cps/apply/apply.dxl and lib/dxl/standard/cps/submit/submit.dxl to execute our code, then run fnCPS_Apply(current Module) (or fnCPS_Submit(current Module)), then execute some more dxl after the user finishes. Currently, we've got it working in 7.1 and we are testing for 8.1.
I'm having the problem where after calling the fnCPS_Submit(current Module) function, the execution stops and nothing after the call runs. Even if the code is simply adding a print statement after call in the default dxl file, the print statement never runs. AND this only happens for Submit, not Apply.
Has anyone else used such a setup and had this problem with 8.1?
Edited: 26-Sep-2006 at 19:10 by Justin Gravois |
|
![]() |
|
![]() |
|
Bad news I am afraid.
In DOORS 7, the sumbit dialog was modal, i.e. block() was used to diaplay the dialog, this meant that execution continued from that point in the DXL after a call to release(). In Doors 8.1, the dialog is displayed using show(), which means that execution does not continue past that point. This is why your code does not work any more. I am not sure what you can do about it since the source code is encrypted. The apply dialog is still modal. I wonder why they decided to make the submit dialog non-modal? ------------------------- Tony Goodman http://www.smartdxl.com Edited: 27-Sep-2006 at 09:04 by Tony Goodman |
|
![]() |
Telelogic DOORS
» Change Management
»
Custom CP Scripting
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.