![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: OLE changes between baselines Topic Summary: Created On: 31-Mar-2004 18:15 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
We are currently migrating from V5.2 to V7.0 and I have a small problem with one of my scripts. I had extended the basic Baseline comparison script to compare more attributes and output its results to a file which I can view as a tabular list of changes.
I also used the history functions to include messages in the log when an OLE had been inserted, modified or deleted. In 7.0 I can cover insertions and deletions by comparing the oleCount results for the two baselines but I can't find a way of detecting modifications because there are no longer any insertOLE, pasteOLE or changeOLE events generated in the History. Does anyone know how I can tell whether the OLE in one object has been modified from the one in the baseline copy of that object. Thanks Jon ------------------------- Jonathan Marshall EADS Astrium |
|
![]() |
|
![]() |
|
Jonathan,
In your DOORS v7.0 database, have an Administrator right click on the database root to check the Properties. Under the "General" tab, make sure you have "Save OLE Objects in attribute history" checked. If it is not, this might be the problem. ------------------------- Michael Sutherland michael@galactic-solutions.com http://galactic-solutions.com |
|
![]() |
|
![]() |
|
Did some testing a couple years ago. Attach find the raw code. I didn't run it recently and no doubt it needs to be tweaked just to run.
No doubt you've got to get an object with Object Text with a couple OLE in it. If you save these guys as files you can compare the files to see if they are the same. - Louie |
|
![]() |
|
![]() |
|
Michael,
Thanks but I already tried that. With "Save OLE Objects in attribute history" checked you get the OLE in the text change history records so you could put an old OLE back by restoring the pre change text but you still don't get the insertOLE, pasteOLE or changeOLE events so you are still left trying to decide if an OLE in one text field is the same as one in another. Jon ------------------------- Jonathan Marshall EADS Astrium |
|
![]() |
|
![]() |
|
Forgot to add: Text has changed when the richTextNoOle() give different results; or when the embedded OLEs that were exported to Files (see above code) are not the same. richTextWithOle() almost ALWAYS gives different results even when one object is copied to another (and therefore should be the same).
- Louie |
|
![]() |
|
![]() |
|
Louie,
Thanks I've got something which works most of the time now based on comparing the lengths of the strings returned by richTextWithOle if all my other checks say that the objects are the same. Its not perfect, I can think of a couple of ways to fool it, but its better than nothing and it should flag most of the changes. Jon ------------------------- Jonathan Marshall EADS Astrium |
|
![]() |
|
![]() |
|
John,
I am looking for a DXL that will compare more attributes than the default 'compare baseline' tool provided with V7.1. Do you have an example that I could use as a starting point? Thanks, Karl |
|
![]() |
|
![]() |
|
It seems funny that so many people want to do this, but it isn't a standard feature in DOORS.
For DOORS 6, I get the attribute's rich text with a call to richTextWithOle, then do a regular expression to extract the bit that has the ole in: Regexp startRegexp = regexp "\\{\\\\pict\\\\wmetafile[^}]*" I then compare the string obtained from the first match from the two different attributes. This has worked for me in my testing so far. Edited: 3-Nov-2004 at 16:28 by Richard Brecknell |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
OLE changes between baselines
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.