Things can get worse if I change the test to API2. Changed the class to descend from DesktopListbox instead of Listbox, Now it doesn’t fire even once as before.
create container control with a listbox.
add user definition ueCellTextPaint to listbox
in the listbox CellTextPaint definition add the code: ueCellTextPaint
whenever CellTextPaint is called it will call your user event ueCelltextPaint.
use this container control in a window, and call it lets say ‘lbGroups’.
in this container control now you can select the user definition ueCelltextPaint and put some code in it.
hope it makes more sense now …
I mean by userEvent = user definition
in the listbox CellTextPaint definition add the code: ueCellTextPaint
whenever CellTextPaint is called it will call your user event ueCelltextPaint.
Thats clear, and thats why it makes no sense.
if I call the parents ueCelltextPaint in CellTextPaint, there is no point having the class.
I may as well just put my special code there.
What I need to happen is
Class CellTextPaint event happens, and MAY require return true
Then Listbox normal event fires, and returns true if the class did.
We are now having two conversations, however, so Im dropping my class idea.
It was, I preset it with content in the properties inspector, and proven it was ok when I painted them in different colors. I was induced to error by the debug window that has hidden my DebugLog tests only presenting ONE line instead of a list of them. If you follow and read with detail all the posts I made here you will understand what occurred.