My understanding is that itemInfo is a method that extracts limited
information about a tree item, but there seems to be no way to store
additional data with an individual item. My thinking is that when doing
dynamic loading of child data during an expansion of a parent, if the means
to load that data could be described in the form of an object stored as
parent itemInfo data it would provide improved encapsulation and less code
dependencies. Is there an alternative?
Staffan
------------------------------------------------------------------------------
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
