![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: move object via DXL not sticking Topic Summary: Can't move objects via DXL Created On: 28-Feb-2006 23:51 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Not sure if this helps, but there is a known problem with using move() to move object between lockable sections. This is fixed in DOORS 8.0. You can always use cut and then paste instead of move(). | |
![]() |
|
I wrote a script that moves one object after another using DXL's move(object o1, object o2) function. This moves object o1 after object o2. It works, until I close and reopen the module. When the module is reopened, the moves never happened. Even the object history of object o1 doesn't show the move.
I am using DOORS 7.1.1167.0. Any suggestions on whether I'm doing anything wrong? Really simple sample code below. //begin code Object src = object(2799) Object dst = object(2312) move (src, dst) //end code ------------------------- Kevin Murphy http://www.baselinesinc.com The Requirements Management Experts |
|
![]() |
|
![]() |
|
You have to save the changes to be persistent.
|
|
![]() |
|
![]() |
|
Ron,
Thank you for the response. However, saving via DXL or manually doesn't fix this. I added the following to the code above: //begin code save (current module) //end code and no change in results. Any other ideas? ------------------------- Kevin Murphy http://www.baselinesinc.com The Requirements Management Experts |
|
![]() |
|
![]() |
|
Long shot here, but insert the following before your save: print "Current = " (name(current Module)) "\n".
Current is a flakey thing. Scripts that require a current module should do something like this at the top: Module mCurr = current if (null mCurr){infoBx("Run from open module"); halt} Thereafter, us mCurr and don't use "current Module". When I manually move I get a "Move Object" history record; when I move with DXL I get an "Arrange Module" history record; one that I've never seen. Anyway saving seems to work for me. - Louie |
|
![]() |
|
![]() |
|
A little experimenting I found this: manually moving an object generates an object history of type "clipMoveObject" whose goodStringOf is "Move Object", as displayed in History. Moving an object with DXL results in a module level History of type "moveObject" whose goodStringOf is "Arrange Module", as displayed in History. Notice Arrange Module is not associated with the object; and that's odd.
When you move the object with DXL, goto Module Properties, History, select all, and look at the last History. You should see an "Arrange Module" history. Close and reopen and see if that's still there. - Louie |
|
![]() |
|
![]() |
|
Not sure if this helps, but there is a known problem with using move() to move object between lockable sections. This is fixed in DOORS 8.0.
You can always use cut and then paste instead of move(). ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
Tony,
I think that's the problem. I'm working with objects in lockable sections in fairly large modules. I wrote this utility to avoid using cut and paste. I haven't had time to test this recently, so I'll check out Louie's suggestion. ------------------------- Kevin Murphy http://www.baselinesinc.com The Requirements Management Experts |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
move object via DXL not sticking
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.