![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: moveObject History Topic Summary: Created On: 5-Feb-2008 21:02 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
My classified partners are excercising my DXL on DOORS v8.3. One script aborted when faced with a 'moveObject' History Type (not to be confused with a 'clipMoveObject' type) from back in the v6.1 days. I have no access to the object in question. Ive been trying in v5.2 and v7.1 and v8.1 and cannot reproduce that History.
'clipMoveObject' looks like 'Move Object' in the GUI. 'moveObject' looks like 'Arrange Module', as far as I can tell. When I drag and drop an object, I get a 'clipMoveObject' History. When I use the dxl 'move(o1, o2)' command, I oddly get no History at all. Anyone have any idea how I can recreate a 'moveObject' History? Any idea how to move objects, other than drag and drop and DXL? - Louie Anyhow, I see with much curiosity that the v8.3 DXL manual has no reference to HistoryType 'moveObject', whereas the v8.1 DXL manual does. That makes me suspect Telelogic has done something which most of us would consider a 'bug'. |
|
![]() |
|
![]() |
|
My 8.1 dxl manual does not reference moveObject as you can see in the following list:
Constants (history type) Declaration const HistoryType unknown const HistoryType createType const HistoryType modifyType const HistoryType deleteType const HistoryType createAttr const HistoryType modifyAttr const HistoryType deleteAttr const HistoryType createObject const HistoryType copyObject const HistoryType modifyObject const HistoryType deleteObject const HistoryType unDeleteObject const HistoryType purgeObject const HistoryType clipCutObject const HistoryType clipMoveObject const HistoryType clipCopyObject const HistoryType createModule const HistoryType baselineModule const HistoryType partitionModule const HistoryType acceptModule const HistoryType returnModule const HistoryType rejoinModule const HistoryType createLink const HistoryType modifyLink const HistoryType deleteLink const HistoryType insertOLE const HistoryType removeOLE const HistoryType changeOLE const HistoryType pasteOLE const HistoryType cutOLE const HistoryType readLocked |
|
![]() |
|
![]() |
|
Typo, its in the v7.1 DXL manual. Pulled out my old v7.1 printed manual and I see that I wrote a note indicating that 'moveObject' was created by DXL and looks like 'Arrange Module', and that 'clipMoveObject' is created manually and looks like 'Move Object'. Still cannot reproduce it; guess I need to install v6.1 and try it there.
- Louie |
|
![]() |
|
![]() |
|
False Alarm, I've figured it out. In v8.1 and earlier, there was a DOORS bug that when you use DXL to 'move' an object, the History.absNo field incorrectly stated '0' instead of the AbsNo of the object moved. Thus such History appeared in the Module properties and not the Object properties. I thought no such History was generated since I was looking at the Object Properties, where I could see manual move History but no DXL move history.
I see this bug is fixed in v8.2 and v8.3. The DXL move history 'moveObject' identifies the object in the History.absNo field. The manual click-and-drag history 'clipMoveObject' identifies the object, oddly, in the History.oldAbsNo field. Don't know any other History types that use oldAbsNo; maybe I should check the various 'paste' Histories. The bug, no surprise, continues for old History if you archive a v7.1 module and restore it in a v8.3 database. I didn't try it but believe 'migrating' will likewise preserve the old bug. New History, of course, will start using absNo correctly. Odd they removed 'moveObject' from the DXL manual, that was no doubt an oversight. - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
moveObject History
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.