Wave wrote:

>
> Being mostly ignorant to CE wouldn't a commandID have to be  
> attached to
> every control in order to make them generate an event.

I think so. Yes.

AFAICS, we either have to install a control hit event on every  
control or attach a commandID to every control. Going the commandID  
route means the window containing the control must have the standard  
handler attribute, whereas kEventControlHit will work in any window.

> How are dynamically generated controls affected in terms of ease of  
> use?

I don't know.

bw





> -----Original Message-----
> From: Bernie [mailto:fblist@...]
> Sent: Wednesday, November 30, 2005 6:04 AM
> To: futurebasic@...
> Subject: [FB] kEventControlHit v kEventCommandProcess
>
>
> Dear Carbon Eventers,
>
> I'm updating TWM to give my user the option to generate CE code.
>
> We can detect a control hit in a couple of ways... install
> kEventControlHit or set a command id to the control and pick it up
> with kEventCommandProcess. I'm trying to keep this update as simple
> (for myself) as possible so I want to go with one or the other (no
> user choice) for the generated code. Personally, I think commandID/
> kEventCommandProcess but what think you?
>
> btw, all windows will have the standard handler attribute.
>
> TIA
> Bernie
>
> <http://homepage.ntlworld.com/bernie.w/twm.htm>
>