Bionic Badger wrote: >> to start such an action, is an easy thing to change) >> > > Yes, that's it. Is there any way to override the input for a tool > with something simple like the event table? > The RightDown is intercepted in a2dMasterToolZoomFirst or a2dMasterDrawSelectFirst. and redirects it to PushZoomTool.
a2dZoomTool::OnMouseEvent does the thing. The OnMouseEvent you can redefine in your derived a2dYourZoomTool. Same for a2dMasterToolZoomFirst:OnMouse. So yes you can. But you can also just copy those tools to your own app., and redefine what you want. Master tools are more like steering other tools, still they work together and the other tools also react to keys/mouse events in certain ways, i think was what worked. Many variation are possible. See the tools as examples, and derived or use what fits you. It is the mechanism of tools interacting with each other what is important to understand, also complicated. But complication is the price to pay in order to be flexible, which is required for a library. Writing just an application using some tools, is much more easy, since you know what you want. I tried/try to find ways to allow different behavior, while still give something which might work for most. Klaas ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Wxart2d-users_dev mailing list Wxart2d-users_dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxart2d-users_dev
