Guillaume MM wrote:
>> So without touching this, do you see easy way how to trigger some signal
>> which would issue loading all images in the document, not just on the
>> screen. I could just call such lfun and let lyx work in backgrounds without
>> managing it for 5min; even that would be
Le 19/03/2017 à 22:12, Pavel Sanda a écrit :
Guillaume Munch wrote:
If QFileSystemWatcher works, you see the modification instantly. If it
does not, you now see it when you activate the window.
Hmm this is not what I see here (gcc 4.9.4 & qt 4.8.5).
I need to scroll or cause some movement so
Guillaume Munch wrote:
> I chose a big interval because it is only useful for cases where
> QFileSystemWatcher does not work.
That's fine.
> If QFileSystemWatcher works, you see the modification instantly. If it
> does not, you now see it when you activate the window.
Hmm this is not what I see
Le 11/03/2017 à 20:16, Pavel Sanda a écrit :
Guillaume Munch wrote:
On the other hand, for graphics, the
idea of the previous FileMonitor could be adapted to refresh graphics
when they appear on the screen
Perhaps. But it should do that when window gets active (we already catch that
signal
Guillaume Munch wrote:
> On the other hand, for graphics, the
> idea of the previous FileMonitor could be adapted to refresh graphics
> when they appear on the screen
Perhaps. But it should do that when window gets active (we already catch that
signal for redrawing graphics).
Typical scenario I
Le 11/03/2017 à 08:34, Pavel Sanda a écrit :
Guillaume Munch wrote:
commit 24f68aff8d2ba9139017ca3927eda1f1aaf039af
Author: Guillaume Munch
Date: Sat Mar 11 00:11:02 2017 +0100
Nonsense for whoever insists on using gcc4.6 & qt4.8 in 2017
Does it mean it is not supposed
Guillaume Munch wrote:
> commit 24f68aff8d2ba9139017ca3927eda1f1aaf039af
> Author: Guillaume Munch
> Date: Sat Mar 11 00:11:02 2017 +0100
>
> Nonsense for whoever insists on using gcc4.6 & qt4.8 in 2017
Does it mean it is not supposed to work with those two or it should?
I