> > After trying to debug I discovered that the menu item calls a method that
> > mimics an AWT Enter key press. I guess so that some event lister can update.
> yep, that was the only way to make several tools behave the same. This
> was done because it was not possible to have a slower doubleclick on
> tablet pcs, where the tap of the pen is not the same as a mouseclick.
Okay Cool. We should use the SWT facilities to mimic a KeyPress. Even if all we
do is look up the correct handler for the event and kick the handler.
> This shouldn't give any problems though.
Actually on mac .... we are forced to run with the property headless set to
true; this prevents the custom Apple Swing jars from starting up and
registering a menubar. We need to do this so that SWT can sneak in and register
the top-level menubar.
Setting headless to true is the easiest way to tell the normal Java AWT system
to take a hike.
> > Not sure how to debug this one, can someone take a look.
> > java.awt.AWTException: headless environment
> How is this possible? Why would one be in headless while using the mouse?
See above; it is actually documented as one of the steps required in our
CustomApp tutorial. You need to set this setting as part of defining your
product.
> What are you doing exactly.
>
Levi is trying to work through the tool infrastructure in order to finish up
the "Smart Buffer" tool as per the recent RFC. As part of that we are back to
the original request to add "buffer" to the Point and Line tools so they can be
used on a polygon layer.
Hopefully that summary is enough detail? The inability of the AWT Robot to work
is something that all macs share.
Jody
_______________________________________________
User-friendly Desktop Internet GIS (uDig)
http://udig.refractions.net
http://lists.refractions.net/mailman/listinfo/udig-devel
