![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: \G et children of objects regardless display set Topic Summary: Created On: 17-Sep-2007 14:44 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Kevin, Louie, Thank you both for your help. I restarted the programming of the LDXL script, and tried your examples, and both worked indeed. I found my mistake - an erroneous condition before displaying the actual data. Apparently, I was looking at the wrong location for solving the bug. Sorry... Regards, Sjors | |
![]() |
|
Hi,
I'm creating a LDXL column, which displays - for each object - its children (if there are any). I manage to do this as long as the children are part of the display set. However, as soon as the children are not visible (e.g. when setting the display level), the LDXL column is no longer showing the object's children. I have tried the following three mechanisms: FIRST: for o in obj do { ... } SECOND: Object o = first (obj); o = first (sibling(o)); while (o!=null) { ... o = next (sibling(o)) } THIRD: absolute object addressing, with o = obj [ i ], with i starting at 1, until o = null All three alternatives take current display set into account. Any alternatives, which really look into the database...??? Thanks! Sjors Edited: 17-Sep-2007 at 14:48 by Sjors de Leeuw |
|
![]() |
|
![]() |
|
Sjors,
try for object in entire module do { } You will get deleted objects with this, so you may have to insert something like if (isDeleted o) break in your code. It will also get tables... Let us know how it goes! Kevin ------------------------- Kevin Murphy http://www.baselinesinc.com The Requirements Management Experts |
|
![]() |
|
![]() |
|
Hi Kevin,
Thank you for your swift answer! Either I misunderstand your answer, or you misunderstood the question ;-) Since it's a layout DXL column, I shouldn't browse the complete module for each object that is displayed, right? It looks like your suggestion is an alternative for my first mechanism. However, there I use: for o in obj do { ... } instead of "for o in <module>" (I would expect something like "for o in entire obj do {...}", but it's not existing) Or... did I really misunderstand you? Regards, Sjors |
|
![]() |
|
![]() |
|
By the way:
According to the DXL Manual, the "for o in obj" should ignore filters: Copied from manual: for object in objectSyntaxwhere: Assigns o to each successive child of object parent. This loop ignores filters, such that even if objects are filtered, they are still returned by this function. Deleted objects are included when they are displayed and excluded when they are not displayed. |
|
![]() |
|
![]() |
|
Sjors,
I just tried the following at it worked. I am using DOORS 8.2, and I even filtered and it still worked. ------------------------- Kevin Murphy http://www.baselinesinc.com The Requirements Management Experts |
|
![]() |
|
![]() |
|
Sjors,
By the way, I realize my reply wasn't helpful to you--because it's the very first thing you did. Can you post your code, specifically of example 1 and what didn't work? Can you also take us through the steps you performed? Are you saving this LDXL in a view that is the default view for the module? ------------------------- Kevin Murphy http://www.baselinesinc.com The Requirements Management Experts |
|
![]() |
|
![]() |
|
As other said, the 'for oSub in obj' loop should work, so long as you make an explicit check for deleted:
if (isDeleted(oSub)) continue. It works for me. Perhaps you are calculating the results oddly. Try the attached. - Louie Edited: 17-Sep-2007 at 19:48 by Louie Landale |
|
![]() |
|
![]() |
|
Kevin, Louie,
Thank you both for your help. I restarted the programming of the LDXL script, and tried your examples, and both worked indeed. I found my mistake - an erroneous condition before displaying the actual data. Apparently, I was looking at the wrong location for solving the bug. Sorry... Regards, Sjors |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.