Closed GoogleCodeExporter closed 9 years ago
Tested several times : really not sure if this bug linked with robot.settings()
or not.
Original comment by filim...@gmail.com
on 19 Jun 2008 at 7:10
[deleted comment]
org.fest.swing.exception.ActionFailedException: Event queue is blocked by an
active
AWT PopupMenu
at
org.fest.swing.exception.ActionFailedException.actionFailure(ActionFailedExcepti
on.java:33)
at org.fest.swing.core.AWTEventPoster.postEvent(AWTEventPoster.java:61)
at org.fest.swing.core.RobotFixture.type(RobotFixture.java:447)
at org.fest.swing.core.RobotFixture.enterText(RobotFixture.java:434)
at org.fest.swing.driver.JTextComponentDriver.enterText(JTextComponentDriver.java:97)
at
org.fest.swing.fixture.JTextComponentFixture.enterText(JTextComponentFixture.jav
a:165)
How to reproduce :
1. slow computer
2. type looooong text in non focued window using
JTextComponentFixture.enterText(...)
3. in parallel make cpu consuming task (play with scollbar using mouse,
zip/unzup, etc.)
Original comment by filim...@gmail.com
on 19 Jun 2008 at 7:24
public static boolean isAWTPopupMenuBlocking() {
// Abbot: For now, just do a quick check to see if a PopupMenu is active on w32.
Extend it if we find other common
// situations that might block the EDT, but for now, keep it simple and
restricted to what we've run into.
return /* Bugs.showAWTPopupMenuBlocks() && */isAWTTreeLockHeld();
}
Bugs.showAWTPopupMenuBlocks()
Probably should be uncommended, and introduced ability to configure
Bugs.showAWTPopupMenuBlocks().
Thanks!
Original comment by filim...@gmail.com
on 19 Jun 2008 at 1:37
Wow! Thank you so much for the detailed explanation! It'll make it a lot easier
to fix :)
BTW, can you please send me your name to alex.ruiz.05 at gmail.com. I'd like to
add
to you the contributors list.
Original comment by Alex.Rui...@gmail.com
on 19 Jun 2008 at 2:29
Hi Filimono,
Looking at the code, 'Bugs.showAWTPopupMenuBlocks()' is always true.
Uncommenting it
will not fix the bug. I think the problem is setting the value to 0. I think
the bug
is to discover a minimum value that will let the test run without problems.
Thoughts?
Thanks!
-Alex
Original comment by Alex.Rui...@gmail.com
on 19 Jul 2008 at 4:04
Am i right: it is old version java bug and it is not reproducible in 1.6
anymore? So
why not remove that showAWTPopupMenuBlocks() check?
Original comment by filim...@gmail.com
on 23 Jul 2008 at 4:16
Set the module as a label, instead of being part of the title.
Original comment by Alex.Rui...@gmail.com
on 1 Dec 2008 at 2:04
We'll address this issue in version 1.1.
Original comment by Alex.Rui...@gmail.com
on 4 Dec 2008 at 6:02
Hello,
I am kind of new to the Fest thing.
I have been using FEST for a couple of weeks
I just saw the following:
1. JMenuItemFixture menuItem = ...
2. menuItem.requireVisible();
3. menuItem.click();
And I am facing a hang (no exception apparently).
I moved to RC1, same punishment :(
I tried a lot of things and I am kind of stuck.
Any workaround I can apply to get out of this?
I am on a Mac Java 1.5.
Original comment by bertrand...@hotmail.com
on 31 Dec 2008 at 12:01
Hi Bertrad,
I've been having trouble reproducing this bug. I'd help a lot if you could
please
send me a test case reproducing this defect. My e-mail address is alex.ruiz.05
at
gmail.com. If I can reproduce it, I'll have this fixed before we release 1.0.
Many thanks,
-Alex
Original comment by Alex.Rui...@gmail.com
on 31 Dec 2008 at 8:13
I apologize I misspelled your name :(
Original comment by Alex.Rui...@gmail.com
on 31 Dec 2008 at 8:24
Original comment by Alex.Rui...@gmail.com
on 5 Feb 2009 at 4:58
Original comment by Alex.Rui...@gmail.com
on 5 Feb 2009 at 5:01
Closing this issue. AWT mode is no longer supported. In addition, I never got a
test
case to reproduce this issue.
Original comment by Alex.Rui...@gmail.com
on 14 Feb 2009 at 11:57
Original issue reported on code.google.com by
filim...@gmail.com
on 19 Jun 2008 at 6:54