![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Test Tracking Toolkit Topic Summary: Initiating from DBE callbacks Created On: 13-Jan-2009 14:21 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Hi David, That did the trick and I can now call the various T3 functions from a button call back. Thanks Mark | |
![]() |
|
Hi,
I want to initiate the 5 T3 functions from Button callbacks within a Dialog box rather than via the Tools menu. The existing T3 DXL files simply call the associated include file. Is it is possble to reference these include files from a button callback? Thanks Mark ------------------------- mark_williamson@synthesys.co.uk http://www.synthesys.co.uk ---------------------------------------- |
|
![]() |
|
![]() |
|
Below is the code in Formal.dxl that creates the menu options. So you need to go to those dxl files and see what they do. Then create your button callbacks to run the code in those files.
------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
Hi David,
I have examined these DXL files previously and they simply reference the associated include file, ie #include <standard/testTracking/t3_setup.inc>. I can run this quite happily from a formal module dxl window but my issue is how do I call this functionality from a DBE callback? With the #include <standard/testTracking/t3_setup.inc> within a call back function a non local variable error is generated. Mark ------------------------- mark_williamson@synthesys.co.uk http://www.synthesys.co.uk ---------------------------------------- |
|
![]() |
|
![]() |
|
You cannot do an include for a button callback. You can try doing "eval_(runFile(<filename>
![]() ![]() ------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
Try
runStr("#include <standard/testTracking/t3_setup.inc>") I would also protect the calls in the same way they are on the menu. e.g. if (canPurgeObjectsMap == menuAvailable_) { runStr("#include <standard/testTracking/t3_setup.inc>") } ------------------------- Tony Goodman Smart DXL limited www.smartdxl.com |
|
![]() |
|
![]() |
|
Thanks David and Tony,
One step forward and two back.... I'm trying to make the call from within a DXL call back function, but runStr or runFile return an undeclared variable error. The DXL ref manual seems to relate these perms to external applications calling DOORS. Cheers Mark ------------------------- mark_williamson@synthesys.co.uk http://www.synthesys.co.uk ---------------------------------------- |
|
![]() |
|
![]() |
|
Sorry. That should have been "eval_(readFile(<filename>
![]() ------------------------- David Pechacek AAI Services Textron dpechacek@sc-aaicorp.com David.Pechacek@gmail.com |
|
![]() |
|
![]() |
|
Hi David, That did the trick and I can now call the various T3 functions from a button call back.
Thanks Mark ------------------------- mark_williamson@synthesys.co.uk http://www.synthesys.co.uk ---------------------------------------- |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Test Tracking Toolkit
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.