Click and motion events don't seem to be "intercepted and stopped" by handlers. Sometimes you might want that, sometimes not.

Shoes.app do
  click do
    alert "app click"
  end
  stack do
    para "click anywhere for one message"
    flow do
      para "click here for two"
      click do
        alert "flow click"
      end
    end
    button "click here for only one" do
      alert "button click"
    end
    para "click the circle for two messages."
    oval(:radius => 30, :left => 150, :top => 250).click do
      alert "oval click"
    end
  end
end

Is there any general way to make the click-handler on the flow or oval get the click, and not the app? Like the button -- when you click the button the app doesn't get a click too.

Related issue: the app gets the click *first*, before the thing on top of the app.... that's a little counterintuitive.



Reply via email to