What is your treeview parented to?
I find, strangely, that the most prominent messages returned by windows are different based on how many parents they have. For example, my object called entList is currently not parented to the groupbox that it appears to be inside of. This way, it returns all keyboard and mouse events to the main window. This way, I have full control over the object. If I had it actually parented to the groupbox, it would be returning proper events through WM_NOTIFY, which are all mostly events returned as $401. An example of a gadget that returns proper messages is created with SetUp_VarsList. With that list view, there wasn't a reason to get mouse and keyboard events - Just actual gadget events telling me when something has been selected, clicked (fully clicked), etc.
Thus, through the WM_NOTIFY segment of WaitEvent is the best way to get messages, because they are always right and proper. (Whereas, getting click messages is a bit untrustworthy and hack feeling)
I hope that made sense, I always write a bit strangely when I go off on tangents like that :)
So, see if your gadgets are actually recieving some kind of messages, and try to sort it out so they recieve the kind that you want them to recieve.
Winblitz takes a bit of fiddling, but it's well worth it once it's all working!
I find, strangely, that the most prominent messages returned by windows are different based on how many parents they have. For example, my object called entList is currently not parented to the groupbox that it appears to be inside of. This way, it returns all keyboard and mouse events to the main window. This way, I have full control over the object. If I had it actually parented to the groupbox, it would be returning proper events through WM_NOTIFY, which are all mostly events returned as $401. An example of a gadget that returns proper messages is created with SetUp_VarsList. With that list view, there wasn't a reason to get mouse and keyboard events - Just actual gadget events telling me when something has been selected, clicked (fully clicked), etc.
Thus, through the WM_NOTIFY segment of WaitEvent is the best way to get messages, because they are always right and proper. (Whereas, getting click messages is a bit untrustworthy and hack feeling)
I hope that made sense, I always write a bit strangely when I go off on tangents like that :)
So, see if your gadgets are actually recieving some kind of messages, and try to sort it out so they recieve the kind that you want them to recieve.
Winblitz takes a bit of fiddling, but it's well worth it once it's all working!