![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
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 |
![]() |
![]()
|
![]() |
|||
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 |
|||
![]() |
|||
![]() |
|||
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
|
|||
![]() |
|||
![]() |
|||
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 |
|||
![]() |
|||
![]() |
|||
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 |
|||
![]() |
|||
![]() |
|||
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 |
|||
![]() |
|||
![]() |
|||
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 |
|||
![]() |
|||
![]() |
|||
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 |
|||
![]() |
|||
![]() |
|||
Louie,
thank you very much for your input. Following code works fine with great performance. Rgds, Mathias |
|||
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.