![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Different behaviour running DXL from inside vs outside of DOORS Topic Summary: DXL problems from OLE clients Created On: 23-Feb-2005 17:32 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: When you run DXL from the DXL Interaction window, 'current Module' is set to the module from whose menu you invoked the interaction window. When you run DXL via OLE, this is not the case, you have to tell it which module you want to work on, e.g by: Module m = edit("/Path/To/Module") Object o = current m ack number o | |
![]() |
|
see attached message below
Edited: 23-Feb-2005 at 17:39 by Luke Emmet |
|
![]() |
|
![]() |
|
Yes - within Doors I have opened a project and a module - and the DXL runs fine when I paste the following into the "DXL Interaction" box and Run it.
Object startObj = current;ack number startObj I just want to get the same result from an external client. Is it necessary from the OLE interface to programmatically open a project and module - because what I want is for the user to choose a specific object and then to be able to see which one it is from the OLE client. thanks Edited: 24-Feb-2005 at 10:55 by Luke Emmet |
|
![]() |
|
![]() |
|
When you run DXL from the DXL Interaction window, 'current Module' is set to the module from whose menu you invoked the interaction window. When you run DXL via OLE, this is not the case, you have to tell it which module you want to work on, e.g by:
Module m = edit("/Path/To/Module") Object o = current m ack number o |
|
![]() |
|
![]() |
|
Thanks - that did it :-)
|
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.