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
> 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
> >
> > 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
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
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
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
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
> 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
> I finally found some time for making an infrastructure for running sweave
> with our own customizations. As you can see the patch is trivial, but
> I would like to be sure that it works on windows.
Can I download somewhere a binary to test this?
> Currently, the only bug that this fixes is that
Le 17 sept. 10 à 22:42, Gregor GORJANC a écrit :
I do not know what is the current status with direct Sweave support in
LyX. It is some time since I used LyX with Sweave - there was no need
in the last year (had to finnish PhD). I can provide testing, but can
someone point me in the right direct
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
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
Am 19.10.2010 um 03:34 schrieb Pavel Sanda:
> Stephan Witt wrote:
>> Pavel, can you have a look please?
>
> hopefully towards the end of this week. actually it would be really helpful
> if we can proceed in usual incremental manner - different patches for
> different
> issues, its much harder to
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
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
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
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
Peter Kümmel wrote:
> > ahh, you are right. why do you need it btw?
> > pavel
>
> the deps packages from Joost are on this server.
but this is only internal dev-related server which we do not
want to promote between users and regarding its location
we do not want to have any higher net traffic th
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
>
> 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.
>
>
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
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
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
Le 20/10/2010 00:15, Richard Heck a écrit :
It looks like you could push_back the slice outside of the for loop.
I tried something like that, but it seems not to see the cells when you
go back through.
Finally, this cries for a Inset::updateMacros virtual method allowing
to move this stuff wh
24 matches
Mail list logo
