Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
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
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
Answer This question was answered by Tony Goodman, on Monday, May 15, 2006 7:44 PM

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().
 28-Feb-2006 23:51
User is offline View Users Profile Print this message


Kevin Murphy

Posts: 206
Joined: 15-Jul-2005

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
Report this to a Moderator Report this to a Moderator
 1-Mar-2006 13:07
User is offline View Users Profile Print this message


ron lewis

Posts: 650
Joined: 20-Sep-2004

You have to save the changes to be persistent.
Report this to a Moderator Report this to a Moderator
 1-Mar-2006 13:33
User is offline View Users Profile Print this message


Kevin Murphy

Posts: 206
Joined: 15-Jul-2005

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
Report this to a Moderator Report this to a Moderator
 1-Mar-2006 21:59
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

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
Report this to a Moderator Report this to a Moderator
 1-Mar-2006 22:14
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

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
Report this to a Moderator Report this to a Moderator
 2-Mar-2006 15:19
User is offline View Users Profile Print this message


Tony Goodman

Posts: 1098
Joined: 12-Sep-2002

Answer 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().

-------------------------
Tony Goodman
http://www.smartdxl.com
Report this to a Moderator Report this to a Moderator
 6-Mar-2006 13:39
User is offline View Users Profile Print this message


Kevin Murphy

Posts: 206
Joined: 15-Jul-2005

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
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.