Sounds good.
Thanks,
-T
On Mon, Aug 31, 2009 at 9:48 AM, Sandro Martini wrote:
> Ah, one last thing:
> to avoid confusion (like at the start of this mail thread), I'll put a
> comment in the FocusTest, on what exception is expected, if not
> objections ...
>
> Sandro
>
Ah, one last thing:
to avoid confusion (like at the start of this mail thread), I'll put a
comment in the FocusTest, on what exception is expected, if not
objections ...
Sandro
Ok, thanks.
Bye
You can work on the trunk now -- the 1.3 candidate has already been tagged.
-T
On Mon, Aug 31, 2009 at 9:37 AM, Sandro Martini wrote:
> The FormTest.
>
> Oh N, I found it:
> I copied the main from the FocusTest, with inside a reference to the
> FocusTest ... ok, ok, it's better, all works go
The FormTest.
Oh N, I found it:
I copied the main from the FocusTest, with inside a reference to the
FocusTest ... ok, ok, it's better, all works good.
So, what do you think on adding a comment in the FocusTest source on
what is expected when run (like expected failures in JUnit tests) ?
Sor
IIRC, the focus test is intended to generate that exception -- it's
verifying that we detect a bad focus traversal policy correctly. Which
other test apps are generating this exception?
-T
On Mon, Aug 31, 2009 at 9:27 AM, Sandro Martini wrote:
> Hi to all,
> I've just synchronized (this morning
Hi to all,
I've just synchronized (this morning) all pivot sources from the
trunk, and for example running the wtk/FocusTest I got the following
exception:
java.lang.RuntimeException: Infinite loop in focus traversal policy
for org.apache.pivot.wtk.BoxPane#14
at org.apache.pivot.wtk.Contai
