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: Layout DXL: Display the Baselined version of each Object
Topic Summary:
Created On: 20-Oct-2008 13:20
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.
 20-Oct-2008 13:20
User is offline View Users Profile Print this message


Mathias Burchardt

Posts: 21
Joined: 17-Sep-2008

Hi all,

after baselining a module, object text has been changed.
I would like to have a view, which displays the baseline version of "object Heading and object Text" and the current version of all other attributes.

I created the following code, which works fine (hard coded Baseline 0.1, "PDR" - looking for the last baseline makes it even slower).
The problem is, that the code is very slow in big modules (feedback time >1second if I click on one object).

Does anybody know of a more simple solution?

Thank you very much

Mathias Burchardt
BeOne Hamburg GmbH
Report this to a Moderator Report this to a Moderator
 20-Oct-2008 13:40
User is offline View Users Profile Print this message


Peter Albert

Posts: 232
Joined: 30-Dec-2005

Hi Mathias,

you are going an extremely complicated way for getting the baselined object, which explains the long feedback time for large modules. You might want to check the

Object object(int absno[,Module m])

perm for short cutting your Skip list based approach. Without testing, some lines à la

int absnum = obj."Absolute Number"
Object bo = object(absnum, base)
if (!null bo)
{
}

should do what your current Skip list and subsequent 'find' do, but significantly faster.

Alternatively, please find attached a layoutDXL script, which you can use to either show attribute values for a selected baseline, or show differences w.r.t. the current version. If called as is, it shows the baselined attribute values / the differences for all attributes displayed in the current view.

Regards,

Peter

versionCompare.inc
versionCompare.inc  (17 KB)

Report this to a Moderator Report this to a Moderator
 20-Oct-2008 14:32
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

If I understand correctly: perhaps you can simply scan through all the History of the object, finding the FIRST one that modifies Object Heading and also Object Text. The 'old' History value will be the value that was saved in the most recent baseline. If no such History exists then that attribute hasn't been modified since baselining. This method doesn't require opening up old baselines.

- Louie
Report this to a Moderator Report this to a Moderator
 20-Oct-2008 14:58
User is offline View Users Profile Print this message


David Pechacek

Posts: 674
Joined: 5-Dec-2006

Also, use Buffers instead of strings. Far faster because it doesn't build up the string table. Just be sure to delete the buffer at the end.

-------------------------
David Pechacek
AAI Services Textron
dpechacek@sc-aaicorp.com
David.Pechacek@gmail.com
Report this to a Moderator Report this to a Moderator
 20-Oct-2008 15:25
User is offline View Users Profile Print this message


Mathias Burchardt

Posts: 21
Joined: 17-Sep-2008

Thank you very much, Peter,

the LayoutDXL in the current version (shown below) is much faster now.

Is there any chance to avoid loading the last baseline for each object separately? - there is still a little response time for navigation through the objects.

Thanks a lot and best Regards
Mathias
Report this to a Moderator Report this to a Moderator
 20-Oct-2008 15:35
User is offline View Users Profile Print this message


Peter Albert

Posts: 232
Joined: 30-Dec-2005

I am not sure whether 'load' creates an overhead when the baseline is already open; to be on the safe side I always use the code attached. Would be interesting to see whether it actually improves the performance.

As Louie pointed out, if you are only interested in the latest baseline, using the History would actually remove the need for loading the baseline completely.

Peter
Report this to a Moderator Report this to a Moderator
 21-Oct-2008 09:24
User is offline View Users Profile Print this message


Mathias Burchardt

Posts: 21
Joined: 17-Sep-2008

Peter,

thank you for your input. The code shown below unfortunately doesn't improve performance.

I will also check on the history advice of Louie.

Best Regards,
Mathias
Report this to a Moderator Report this to a Moderator
 21-Oct-2008 09:40
User is offline View Users Profile Print this message


Mathias Burchardt

Posts: 21
Joined: 17-Sep-2008

Louie,

thank you very much for your input.
Following code works fine with great performance.

Rgds, Mathias
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.