Community
Participate
Working Groups
I believe the JavaDoc for ILazyTreePathContentProvider#updateElement() should mention that the implementation can call TreeViewer#setHasChildren() instead of TreeViewer#setChildCount() if the content provider can more efficiently determine the has-children status than it can the actual number of children. This optimization was made possible by 156883. I think it needs to be advertised so clients can take advantage of it in their implementation of ILazyTreePathContentProvider#updateElement(). In fact, I think clients that use ILazyTreeContentProvider also have access to that optimization. If so, that JavaDoc should be updated, too.
Thank you for filing this bug. Would you be able to contribute a patch, too? http://wiki.eclipse.org/Platform_UI/How_to_Contribute
Created attachment 149484 [details] Proposed javadoc enhancement Certainly. Here you go.
Released to HEAD. Thanks for the patch!
Verified on I20091208-0100 via source code inspection. Thanks for the bug report and the patch, John!
Whoops, forgot to mark as verified.