J.Pietschmann schrieb:
> Keiron Liddle wrote:
>
>> That explains it. The execution is separated between the
>> CommandLineStarter and the AWTStarter and it needs to call exit when
>> being run with the CommandLineStarter but not the AWTStarter.
>
>
> I've added other exits() in the catch clause
Keiron Liddle wrote:
> That explains it. The execution is separated between the
> CommandLineStarter and the AWTStarter and it needs to call exit when
> being run with the CommandLineStarter but not the AWTStarter.
I've added other exits() in the catch clauses. Could
this cause trouble too? For s
On Mon, 2002-07-01 at 21:25, J.Pietschmann wrote:
> Keiron Liddle wrote:
> > You do know that every second person will complain that FOP "hangs" if
> > you remove this. :/
>
> The exit() Oleg complained about was inserted by me.
> No problem with removing it, the real exit(0) is in
> the CommandL
Keiron Liddle wrote:
> You do know that every second person will complain that FOP "hangs" if
> you remove this. :/
The exit() Oleg complained about was inserted by me.
No problem with removing it, the real exit(0) is in
the CommandLineStarter (odd place...).
J.Pietschmann
---
Keiron Liddle schrieb:
> On Mon, 2002-07-01 at 16:54, Christian Geisert wrote:
>
>>Simplest solution seems to be to remove System.exit(0) from Fop.java
>>(I'll committ this together with Oleg's patch)
>
>
> You do know that every second person will complain that FOP "hangs" if
> you remove this
On Mon, 2002-07-01 at 16:54, Christian Geisert wrote:
> Simplest solution seems to be to remove System.exit(0) from Fop.java
> (I'll committ this together with Oleg's patch)
You do know that every second person will complain that FOP "hangs" if
you remove this. :/
> Christian
Oleg Tkachenko schrieb:
> Hello!
>
> btw, I've just noticed AWT previewer is broken in cvs maintenance
> branch. Actually the previewer itself is ok, but it is closed when page
I noticed this while testing your patch ;-)
> is ready to show due to System.exit(0) at the end of Fop.java main
>
