![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Detecting changes to OLE Objects in DOORS 7v1 Topic Summary: Created On: 20-Sep-2005 00:42 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi,
Once upon a time back in the days of version 5, DOORS used one of several history types to record the insertion, removal or modification to an embeded OLE object - this was handy for differentiating changes between Object Text and an OLE Object. DOORS 7v1 records the insertion, removal or modification of an embeded OLE object as a change to the Object Text attribute, however, the DOORS 7v1 DXL manual still identifies history type constants for the insertion, removal or modification of an embeded OLE object. So is this now the way it is or is there some trick to differentiating between a change to an OLE object and a change to Object text using DXL? ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz |
|
![]() |
|
![]() |
|
Not using History. ..err.. not using History types.
You could theoretically get the rich text of the before and the after of each such History that modifies a Text attribute. Then save each paired embedded OLE to a file and then read the files to insure they are identical. I went that route once and gave it up as far too time consuming. A reasonable alternative would be to get the rich and the raw text of each from-to of History. If the Raw is the same and the Rich contains OLEs, you could deduce the OLE likely was changed (rather than just bolding some text). - Louie |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Detecting changes to OLE Objects in DOORS 7v1
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.