Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

Am Samstag, den 23.10.2010, 12:52 +0200 schrieb Peter Kümmel: > Am Freitag, den 22.10.2010, 16:44 +0200 schrieb Pavel Sanda: > > Richard Heck wrote: > > > Along these same lines, I wonder if we should pop up an info box when > > > the export is done. If it takes a while, then the user may not notic

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

Am Freitag, den 22.10.2010, 16:44 +0200 schrieb Pavel Sanda: > Richard Heck wrote: > > Along these same lines, I wonder if we should pop up an info box when > > the export is done. If it takes a while, then the user may not notice the > > status message, and those get over-written quickly, anyway.

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

i suppose for the same reason that we cannot have a pointing finger when the mouse hovers something clickable... On 2010-10-22, Pavel Sanda wrote: > Richard Heck wrote: >> Along these same lines, I wonder if we should pop up an info box when >> the export is done. If it takes a while, then the us

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

Richard Heck wrote: > Along these same lines, I wonder if we should pop up an info box when > the export is done. If it takes a while, then the user may not notice the > status message, and those get over-written quickly, anyway. > > In a way, that would solve this issue: It's still going until you

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 10/21/2010 07:17 PM, Vincent van Ravesteijn wrote: Status bar: Moving icons. Text. Messages. Op 22 okt 2010 01:13 schreef "Pavel Sanda" >: Richard Heck wrote: > On 10/20/2010 08:59 PM, Peter Kümmel wrote: >> Am Dienstag, den 19.10.2010, 20... i checked that export wo

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

Guenter Milde wrote: > > Status bar: Moving icons. Text. Messages. > > greyed out (or otherwise modified) export toolbar buttons? wont help in case you use only menu. pavel

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 2010-10-21, Vincent van Ravesteijn wrote: > > but now we have new problem - how to notice user that exporting is still > in progress or finished (some subvserion of hourglass cursor?). > Status bar: Moving icons. Text. Messages. greyed out (or otherwise modified) export toolbar buttons? Günt

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

Status bar: Moving icons. Text. Messages. Op 22 okt 2010 01:13 schreef "Pavel Sanda" : Richard Heck wrote: > On 10/20/2010 08:59 PM, Peter Kümmel wrote: >> Am Dienstag, den 19.10.2010, 20... i checked that export works on simple document here too. but now we have new problem - how to notice user

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

Richard Heck wrote: > On 10/20/2010 08:59 PM, Peter Kümmel wrote: >> Am Dienstag, den 19.10.2010, 20:40 -0400 schrieb Richard Heck: >> >>> I think what's happening is this. If you export pdf (say) without there >>> already being a pdf file there, then everything is fine. But if the pdf >>> file

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 10/20/2010 08:59 PM, Peter Kümmel wrote: Am Dienstag, den 19.10.2010, 20:40 -0400 schrieb Richard Heck: I think what's happening is this. If you export pdf (say) without there already being a pdf file there, then everything is fine. But if the pdf file exists, then LyX will try to ask the

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 20/10/2010 9:17 PM, Peter Kuemmel wrote: You are right, I've not updated the .am files when moving the files. It's fixed (but not tested) now. Peter It compiles, thanks! -- Julien

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

> You have added > Asrc/frontends/qt4/InGuiThread.h > Asrc/frontends/qt4/InGuiThread.cpp > > and modified > Usrc/support/Makefile.am > > Regards, > Julien > You are right, I've not updated the .am files when moving the files. It's fixed (but not tested) now. Peter -- GRATIS! Mov

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

> > > > I personally believe that nested event loops are always evil. > > In this case I'd completely stop the export, let the gui pop up > > the dialog, and on confirmation re-initiate the export process > > with a 'force' flag or such. > > I think the necessity of bidirectional core-gui commun

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 20/10/2010 8:16 PM, Peter Kümmel wrote: whenever in a thread frontend::Alert could send a signal that would be caught by GuiView in the main thread. Once sent the thread would sleep up until it receives a signal from GuiView. Upon reception of the signal, GuiView would execute the required A

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

Am Dienstag, den 19.10.2010, 20:40 -0400 schrieb Richard Heck: > I think what's happening is this. If you export pdf (say) without there > already being a pdf file there, then everything is fine. But if the pdf > file exists, then LyX will try to ask the user whether to overwrite. > This means

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 10/20/2010 08:33 PM, Peter Kümmel wrote: On 20.10.2010 14:02, Richard Heck wrote: On 10/20/2010 05:44 AM, Pavel Sanda wrote: Peter Kümmel wrote: I agree. But this would mean that all dialog related code must be removed from the export functions... which would be a good th

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 20.10.2010 14:02, Richard Heck wrote: > On 10/20/2010 05:44 AM, Pavel Sanda wrote: >> Peter Kümmel wrote: >> I agree. But this would mean that all dialog related code must be removed from the export functions... which would be a good thing in itself but is a bit more involved

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

> whenever in a thread frontend::Alert could send a signal that would be > caught by GuiView in the main thread. Once sent the thread would sleep > up until it receives a signal from GuiView. Upon reception of the > signal, GuiView would execute the required Alert dialog and send a > signal wh

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 10/20/2010 04:24 PM, Abdelrazak Younes wrote: On 20/10/2010 13:51, Richard Heck wrote: I don't know enough about this to know if this is a silly idea or not, but I'll mention it anyway. The dialogs we are discussing are all of the frontend::Alert variety. Indeed, unless I am mistaken, th

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 20/10/2010 13:51, Richard Heck wrote: On 10/20/2010 04:37 AM, Andre Poenitz wrote: On Wed, Oct 20, 2010 at 03:54:03AM +0200, Peter Kümmel wrote: I think what's happening is this. If you export pdf (say) without there already being a pdf file there, then everything is fine. But if the pdf

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 10/20/2010 05:44 AM, Pavel Sanda wrote: Peter Kümmel wrote: I agree. But this would mean that all dialog related code must be removed from the export functions... which would be a good thing in itself but is a bit more involved than what was originally thought. The "box" is open

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 10/20/2010 04:37 AM, Andre Poenitz wrote: On Wed, Oct 20, 2010 at 03:54:03AM +0200, Peter Kümmel wrote: I think what's happening is this. If you export pdf (say) without there already being a pdf file there, then everything is fine. But if the pdf file exists, then LyX will try to

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 10/20/2010 04:37 AM, Andre Poenitz wrote: On Wed, Oct 20, 2010 at 03:54:03AM +0200, Peter Kümmel wrote: I think what's happening is this. If you export pdf (say) without there already being a pdf file there, then everything is fine. But if the pdf file exists, then LyX will try to

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On Wed, Oct 20, 2010 at 11:00:46AM +0200, Andre Poenitz wrote: > I think the necessity of bidirectional core-gui communication would > be gone, if the core were driven by the gui, not the other way round: > > In core (pseudo code): > > Result Buffer::export(File file) > { > // No

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

Peter Kümmel wrote: > > > > I agree. But this would mean that all dialog related code must be > > removed from the export functions... which would be a good thing in > > itself but is a bit more involved than what was originally thought. > > The "box" is open again ;) ouch. is there easy way t

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

> > I agree. But this would mean that all dialog related code must be > removed from the export functions... which would be a good thing in > itself but is a bit more involved than what was originally thought. The "box" is open again ;) > > Abdel. > >

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On Wed, Oct 20, 2010 at 10:37:29AM +0200, Andre Poenitz wrote: > On Wed, Oct 20, 2010 at 03:54:03AM +0200, Peter Kümmel wrote: > > > > > I think what's happening is this. If you export pdf (say) without there > > > already being a pdf file there, then everything is fine. But if the pdf > > > fi

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 10/20/2010 10:37 AM, Andre Poenitz wrote: On Wed, Oct 20, 2010 at 03:54:03AM +0200, Peter Kümmel wrote: I think what's happening is this. If you export pdf (say) without there already being a pdf file there, then everything is fine. But if the pdf file exists, then LyX will try to

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On Wed, Oct 20, 2010 at 03:54:03AM +0200, Peter Kümmel wrote: > > > I think what's happening is this. If you export pdf (say) without there > > already being a pdf file there, then everything is fine. But if the pdf > > file exists, then LyX will try to ask the user whether to overwrite. > > T

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

> I think what's happening is this. If you export pdf (say) without there > already being a pdf file there, then everything is fine. But if the pdf > file exists, then LyX will try to ask the user whether to overwrite. > This means creating a dialog as a child of the parent. But the parent, >

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 10/19/2010 07:08 PM, Peter Kümmel wrote: Am Dienstag, den 19.10.2010, 17:32 -0400 schrieb Richard Heck: On 10/19/2010 04:32 PM, Uwe Stöhr wrote: When exporting I get now tons of this message in the LyX console: QObject::startTimer: timers cannot be started from another thread QApp

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

Am Dienstag, den 19.10.2010, 17:32 -0400 schrieb Richard Heck: > On 10/19/2010 04:32 PM, Uwe Stöhr wrote: > > When exporting I get now tons of this message in the LyX console: > > > > QObject::startTimer: timers cannot be started from another thread > > QApplication: Object event filter cannot be i

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 10/19/2010 04:32 PM, Uwe Stöhr wrote: When exporting I get now tons of this message in the LyX console: QObject::startTimer: timers cannot be started from another thread QApplication: Object event filter cannot be in a different thread. When I first view a file (the Math manual) and then exp

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

When exporting I get now tons of this message in the LyX console: QObject::startTimer: timers cannot be started from another thread QApplication: Object event filter cannot be in a different thread. When I first view a file (the Math manual) and then export it subsequently, I also get this: QO

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 10/19/2010 09:12 AM, Pavel Sanda wrote: Peter Kümmel wrote: On 19.10.2010 08:42, Peter Kümmel wrote: On 19.10.2010 00:05, Uwe Stöhr wrote: > OK, committed a fix, but it needs testing. Now exporting is broken: I don't get a PDF when e.g. exporting the UserGuide to PDF

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

Peter Kümmel wrote: > On 19.10.2010 08:42, Peter Kümmel wrote: > > On 19.10.2010 00:05, Uwe Stöhr wrote: > >> > OK, committed a fix, but it needs testing. > >> > >> Now exporting is broken: I don't get a PDF when e.g. exporting the > >> UserGuide to PDF (pdflatex). > > > > Maybe the pdf is now i

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 19.10.2010 08:42, Peter Kümmel wrote: > On 19.10.2010 00:05, Uwe Stöhr wrote: >> > OK, committed a fix, but it needs testing. >> >> Now exporting is broken: I don't get a PDF when e.g. exporting the UserGuide >> to PDF (pdflatex). > > Maybe the pdf is now in the temp folder. Because the only

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 19.10.2010 00:05, Uwe Stöhr wrote: > > OK, committed a fix, but it needs testing. > > Now exporting is broken: I don't get a PDF when e.g. exporting the UserGuide > to PDF (pdflatex). Maybe the pdf is now in the temp folder. Because the only difference I see is a flag in doExport. > > reg

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

> OK, committed a fix, but it needs testing. Now exporting is broken: I don't get a PDF when e.g. exporting the UserGuide to PDF (pdflatex). regards Uwe

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

Am Sonntag, den 17.10.2010, 17:52 -0400 schrieb Richard Heck: > On 10/17/2010 04:19 PM, Pavel Sanda wrote: > > Peter Kümmel wrote: > > > >> #412: Opening the box of QProcess short before a release? > >> I don't know if this is a good idea. We had so much problems > >> when introducing unblocked

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

Richard Heck wrote: > I could be wrong, but it seems to me that the problems must have lay mostly > at (i). But (i) is the same both times. that was my naive view too, haven't seen the code. if its true we can try it, but this must go soon to have some testing time. pavel

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 10/17/2010 04:19 PM, Pavel Sanda wrote: Peter Kümmel wrote: #412: Opening the box of QProcess short before a release? I don't know if this is a good idea. We had so much problems when introducing unblocked texing, so I think we should postpone it. i thought that once we have it for

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

Am Sonntag, den 17.10.2010, 22:19 +0200 schrieb Pavel Sanda: > Peter Kümmel wrote: > > #412: Opening the box of QProcess short before a release? > > I don't know if this is a good idea. We had so much problems > > when introducing unblocked texing, so I think we should > > postpone it. > > i tho

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

Peter Kümmel wrote: > #412: Opening the box of QProcess short before a release? > I don't know if this is a good idea. We had so much problems > when introducing unblocked texing, so I think we should > postpone it. i thought that once we have it for viewing, it might be piece of cake to add exp

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

Am Sonntag, den 17.10.2010, 18:32 +0200 schrieb Pavel Sanda: > kuem...@lyx.org wrote: > > Author: kuemmel > > Date: Sun Oct 17 12:44:53 2010 > > New Revision: 35662 > > URL: http://www.lyx.org/trac/changeset/35662 > > > > Log: > > Use DispatchResult also in GuiView::dispatchVC to handle messages.

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

On 10/17/2010 06:44 AM, kuem...@lyx.org wrote: Author: kuemmel Date: Sun Oct 17 12:44:53 2010 New Revision: 35662 URL: http://www.lyx.org/trac/changeset/35662 Log: Use DispatchResult also in GuiView::dispatchVC to handle messages. Make it possible to suppress messages stored in DispatchResult ob

Re: r35662 - in lyx-devel/trunk/src: . frontends/qt4

kuem...@lyx.org wrote: > Author: kuemmel > Date: Sun Oct 17 12:44:53 2010 > New Revision: 35662 > URL: http://www.lyx.org/trac/changeset/35662 > > Log: > Use DispatchResult also in GuiView::dispatchVC to handle messages. > Make it possible to suppress messages stored in DispatchResult objects. > B