Bernie wrote: > Couple of annoying 'features' with a data browser in a window with > the standard handler attribute. > When the owning window is *not* frontmost: > 1. The scrolling trackpad scrolls the browser. [I'm assuming the > same happens with the mouse wheel but I have no way of checking this]. > 2. A click on say a checkbox in the browser toggles the checkbox. > To eliminate these, I've installed three events on the browser, > kEventControlClick, kEventMouseWheelMoved & kEventTrackpadScrolled. > Anyone got better ideas? May we assume that you are posting because you think your control click handler sucks? If so, then I agree :-) The official way is to install a kEventWindowGetClickActivation handler, and pass back (i.e. call SetEventParameter with) a ClickActivationResult of kActivateAndIgnoreClick. I have the opposite problem with clicks on a DataBrowser in a non- front window: a click in an empty part of the DB does nothing at all, whereas it should activate the window. I suspect that the handler you are about to write will solve my problem, so please post the code. Robert P.