t we get a nice backtrace. (hopefully)
- lyx::abort();
- return 0; // Solaris CC wants us to return something
+
+ // we really have to survive these (bug #245)
+ if (xeev->error_code != BadWindow) {
+ // By doing an abort we get a nice backtrace. (hopeful
On Wed, Feb 27, 2002 at 07:06:51PM +, Angus Leeming wrote:
> Anyway, this isn't going to break anything is it? Shall I just apply it and
> we'll see if the compliants go away?
yes (btw, there is still the XSync in file dialog, I dno't know if it's helpful
> Do we still need the processEven
On Wednesday 27 February 2002 6:18 pm, John Levon wrote:
>
> please try the attached workaround and try and reproduce the problem
>
> thanks
> john
Anyway, this isn't going to break anything is it? Shall I just apply it and
we'll see if the compliants go away?
Do we still need the processEven
On Wednesday 27 February 2002 6:57 pm, John Levon wrote:
> On Wed, Feb 27, 2002 at 06:56:31PM +, Angus Leeming wrote:
>
> > I know that this isn't in the spirit you would like, but I HATE goto
> > statements. They give me nightmares about my fortran coding days.
>
> this is really just exce
On Wed, Feb 27, 2002 at 06:57:39PM +, John Levon wrote:
> This particular use of goto's is IMHO perfectly sane, and perfectly readable.
but in this case I can just use break anyway ...
john
--
"This is just the kind of crackpot scheme I've been looking to champion!!!"
- P.M. Hartk
On Wed, Feb 27, 2002 at 06:56:31PM +, Angus Leeming wrote:
> I know that this isn't in the spirit you would like, but I HATE goto
> statements. They give me nightmares about my fortran coding days.
this is really just exception-style without real exceptions. The alternative
is duplicating c
On Wednesday 27 February 2002 6:49 pm, John Levon wrote:
> On Wed, Feb 27, 2002 at 06:18:13PM +, John Levon wrote:
>
> > +out:
> > + GUIRunTime::processEvents();
> > + XSync(fl_get_display(), false);
> > + return ret;
> > }
>
> actually remove the processEvents() - it breaks double cl
On Wed, Feb 27, 2002 at 06:18:13PM +, John Levon wrote:
> +out:
> + GUIRunTime::processEvents();
> + XSync(fl_get_display(), false);
> + return ret;
> }
actually remove the processEvents() - it breaks double click and hopefully
isn't necessary
john
--
"This is just the kind o
please try the attached workaround and try and reproduce the problem
thanks
john
--
"This is just the kind of crackpot scheme I've been looking to champion!!!"
- P.M. Hartke on 6U campaign
Index: src/frontends/xforms//FormBase.C
===
Dekel Tsur wrote:
> On Mon, Jul 02, 2001 at 12:20:56AM +0200, Eran Tromer wrote:
> > Every once in a while my LyX 1.1.6fix2 crashes with the following
> > message:
...
> Perhaps the crash is due to an incorrect version of your XForms library
> (compiled for glibc 2.0 when your glibc is 2.1).
Upda
> "Dekel" == Dekel Tsur <[EMAIL PROTECTED]> writes:
Dekel> On Mon, Jul 02, 2001 at 12:20:56AM +0200, Eran Tromer wrote:
>> Howdy,
>>
>> Every once in a while my LyX 1.1.6fix2 crashes with the following
>> message:
>>
>> Frequency: about every couple of hours of active work. I'm not able
>>
On Mon, Jul 02, 2001 at 12:20:56AM +0200, Eran Tromer wrote:
> Howdy,
>
> Every once in a while my LyX 1.1.6fix2 crashes with the following
> message:
>
> Frequency: about every couple of hours of active work. I'm not able to
> reproduce it deterministically. It's not related to any specific
> d
Howdy,
Every once in a while my LyX 1.1.6fix2 crashes with the following
message:
---
lyx: Attempting to save document newfile1.lyx as...
/home/eran/newfile1.lyx.emergency
Save seems successful. Phew.
BadWindow (invalid Window parameter
13 matches
Mail list logo
