Reply to thread

Message

<blockquote data-quote="MrSensitive" data-source="post: 44947" data-attributes="member: 10304">Flipit, You must think more along the lines of a game engine.. (a 2D game engine that is..)what I do with all other elements (I don't call them controls) is draw all graphics on a GDI surface..all click handling is done in the main form, and starts by identifying what element has been hit.&nbsp; in the case of a listbox this would be a listitem in the listbox. the listitem can contain actions that need to be executed, or other stuffthe treeview is an exception for now.. the listbox element would contain a arraylist of listitem elements (did not yet thought it through completely...)and in the draw method there should be som sort of logic to determine what listitems are currently visible and draw only those..etc etc..send me the code, maybe I can rewrite it a bit to fit in this structure..thanks..</blockquote>

[QUOTE="MrSensitive, post: 44947, member: 10304"] Flipit, You must think more along the lines of a game engine.. (a 2D game engine that is..) what I do with all other elements (I don't call them controls) is draw all graphics on a GDI surface.. all click handling is done in the main form, and starts by identifying what element has been hit. in the case of a listbox this would be a listitem in the listbox. the listitem can contain actions that need to be executed, or other stuff the treeview is an exception for now.. the listbox element would contain a arraylist of listitem elements (did not yet thought it through completely...) and in the draw method there should be som sort of logic to determine what listitems are currently visible and draw only those.. etc etc.. send me the code, maybe I can rewrite it a bit to fit in this structure.. thanks.. [/QUOTE]

Verification