I added a mouseevent handlers to teh stage and this is what I see when
I click on a textarea:

The MouseEvent's currentTarget is the application root.  The target is
a VBox.  I'm not really sure where this VBox is comming from.  Is it
something automation adds in there?  The TextArea is inside a
FormItem, Form, CustomCanvas, CustomPanel, Canvas, Canvas, Application.

Thanks,
 Geoff

--- In flexcoders@yahoogroups.com, "Sangavi G" <[EMAIL PROTECTED]> wrote:
>
> Hi,
> 
> This happens if there is an invisible container on the top of these
> controls.
> 
> The solution you can try is to add a mouseClick event listener to the
> application stage and find out the container which is overlapping these
> controls. (or you can find this out even in the design view)
> 
> Once you get the container you can try adding the mouseEnabled=false for
> that container.
> 
> Regards,
> Sangavi
> 
> 
> On Sat, May 24, 2008 at 12:08 AM, Geoffrey <[EMAIL PROTECTED]> wrote:
> 
> >   I'm trying to use FunFX(http://funfx.rubyforge.org/) to do some
> > automated testing of our GUI. I noticed that after I add the
> > automation libraries to the compiler options of my main project, I can
> > no longer interact with various parts of the UI using the mouse. This
> > includes textinput, textarea, buttons, numericstepper, etc.
> >
> > I can tab to these controls, but I can not click on them to bring
> > focus to it. Very odd.
> >
> > I've added the libraries in the main project's Additional Compiler
> > Arguments property under Flex Compiler like so:
> > -include-libraries "C:\flex-sdk\frameworks\libs\automation.swc"
> > "C:\flex-sdk\frameworks\libs\automation_agent.swc"
> >
> > Any thought?
> >
> > Geoff
> >
> >  
> >
>


Reply via email to