complexity of finding UI elements with TreeWalker or FindFirst/FindAll in HTML

Hi,

I was amazed to see that it takes plenty of time (~100-200ms) to for GetNextSibling (of TreeWalker) in HTML,so if i am going through 400 siblings it takes forever.

it is also happens if i use element.FindAll.

Does anyone know what can i do to avoid this.

Thanks in advance

[342 byte] By [dudeness] at [2008-2-21]

«« LinkLabel Issue
»» worksheet_change and data validation

# 1

Could you please clarify "in HTML"? What elements are you trying to retrieve?

PeterDonnelly-MSFTUE at 2007-9-3 >

top of Msdn Tech,Software Development for Windows Vista,Microsoft UI Automation...

# 2

I've seen this myself when I try and get all the elements under an IE window.

Kurt L.

KurtM.Landre at 2007-9-3 >

# 3

It seems that it takes a long time just if there are many childrens.
It happens with parent which is table with about 400 customcontrols

There is an option that only this type of customcontrol has some provider
that takes pleanty of time for GetNextSibling

I will update when i have more info

dudeness at 2007-9-3 >

Software Development for Windows Vista Hot Topic

Software Development for Windows Vista New Topic

Software Development for Windows Vista

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech