Inconsistencies between APIs for LogicalTreeHelper and VisualTreeHelper

Why does the VisualTreeHelper provide a getChild(Visual, index) as well
as a getChildCount() method, but the LogicalTreeHelper only provide a
getChildren(DependencyObject) which only returns an IEnumerable? When
I'd really just like the get the logical child at index 0, dealing with
the IEnumerable is quite annoying.

Is there a reason for this API choice? Or were they just developed by
two different people?

Thanks,
Jason

> Is there a reason for this API choice? Or were they just developed by two
> different people?

Mostly the latter, LogicalTreeHelper is not something we think about a lot
(which is why we put in a *Helper class)


--
-Nick Kramer [MSFT]
http://blogs.msdn.com/nickkramer

---
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm


"Jason Dolinger" <jdolinger@lab49.com> wrote in message
news:%23Z%23RDrJGGHA.1552@TK2MSFTNGP10.phx.gbl...
> Why does the VisualTreeHelper provide a getChild(Visual, index) as well as
> a getChildCount() method, but the LogicalTreeHelper only provide a
> getChildren(DependencyObject) which only returns an IEnumerable? When I'd
> really just like the get the logical child at index 0, dealing with the
> IEnumerable is quite annoying.
>
> Is there a reason for this API choice? Or were they just developed by two
> different people?
>
> Thanks,
> Jason