Richard Heck wrote:
> Yes, I know, but that's what I meant about the macros. I'm not sure why we
> even use this constuct:
> lyxerr << stuff
> anymore, instead of:
> LYXERR0(stuff);
> The latter ends the newline that always seems to be needed, and gives the
> file position and stuff, too.
On 01/13/2010 03:38 PM, Pavel Sanda wrote:
Richard Heck wrote:
I guess the only thing to do would be to have a way of locking the stream,
e.g.:
out<< Lock()<< t1a<< t1b<< Unlock();
Things coming from elsewhere could be cached until the lock is released.
Perhaps this is not so diffi
Richard Heck wrote:
> I guess the only thing to do would be to have a way of locking the stream,
> e.g.:
> out << Lock() << t1a << t1b << Unlock();
> Things coming from elsewhere could be cached until the lock is released.
>
> Perhaps this is not so difficult, even, if we use the LYXERR macros
On 01/13/2010 02:07 PM, sa...@lyx.org wrote:
Author: sanda
Date: Wed Jan 13 20:07:18 2010
New Revision: 33013
URL: http://www.lyx.org/trac/changeset/33013
Log:
Move lyxerrFlush() out of singnal/slot business.
Under massive load of lyxerr<< messages we lose synchronization in ui
and messages ge
