4 replies to this topic

[Markus]

Howdy,

I'm wondering what you would expect from this line

CODE

Items[n].Items

Normally, I'd say you want to access all items that are n-th item's childs. But this is not how NextInspector treats items.

Some examples:

CODE

if Items[0].Items[2] = Items[1].Items[2] then
  ShowMessage('Say what?');

CODE

ShowMessage(IntToStr(Items.Count));  // obviously returns count of _all_ items (correct)
ShowMessage(IntToStr(Items[0].Items.Count));  // returns count of _all_ items
ShowMessage(IntToStr(Items[1].Items.Count));  // returns count of _all_ items
ShowMessage(IntToStr(Items[2].Items.Count));  // returns count of _all_ items

Is this (mis)behaviour by design?

Cheers,
Markus

[Boki (Berg)]

Hello Markus,

You are probably using version 4. To obtain count of Child-Items inside Item, use Count property. To access to single item inside item with using relative index use Item.Item[x]

more details:
http://www.bergsoft....es&page=proprun

regards

[Markus]

Hi Boki,

I just wanted to add attention to this misleading behavior. Do you plan to keep it this way?

Cheers,
Markus

[Boki (Berg)]

Hello,

Items property point to the all Items, not to child-items. Maybe I can made this property protected, but this will not be changed.

[Markus]

Hello,

Hello,

Items property point to the all Items, not to child-items. Maybe I can made this property protected, but this will not be changed.

I'm not talking about the items property in general and I'm not saying that Items[n].Items necessarily have to point to n-th item's childs if there are other properties for that. I'm talking about cascaded items properties that make no sense; they're redundant and misleading.

Anyway, just wanted to give suggestions from a customer's point of view.