I can't imagine where I could put a Wait() loop inside a gadget class !? Doing anything inside the dispatcher function blocks the whole Intuition and all the rest.
I'm wondering how the listbrowser gadget handles internally resizing of columns with a mouse ?
My bad. I forgot input events are in a list. I was checking only the first event. So I was wondering I'll get only the first RAWMOUSE event but not anything else. Also the return values have to be correct to keep the gadget active when needed. With input handler I meant adding a handler to the input.device. But I don't need it anymore.
Send a signal or message to your own task to do the actual DoRender() call.
I can't imagine where I could put a Wait() loop inside a gadget class !? Doing anything inside the dispatcher function blocks the whole Intuition and all the rest.
I'm wondering how the listbrowser gadget handles internally resizing of columns with a mouse ?
Please define "input handler".
My definition of an input handler is a routine which gets called by input.device after adding it with an IND_ADDHANDLER command.
From your last reply I suppose you rather mean the GM_HANDLEINPUT method, right? This is not an input handler, it is a method of your gadget class.
I am not familiar with DoRender, but after reading the autodocs I would say it is exactly what you should use.
On OS3 I would use this which I assume is the contents of DoRender:
My bad. I forgot input events are in a list. I was checking only the first event. So I was wondering I'll get only the first RAWMOUSE event but not anything else. Also the return values have to be correct to keep the gadget active when needed. With input handler I meant adding a handler to the input.device. But I don't need it anymore.
Thanks everybody.