Re: [PATCH] make LyXText::status understandable ...

2003-03-14 Thread Andre Poenitz
On Thu, Mar 13, 2003 at 10:23:49PM +, John Levon wrote: > It's a pity to lose the charm of Juergen's comment but I'm just not very > charming ... You could create an "old_comments" file in development ;-) (and rename TodoPlan-1.3 intp TodoPlan-1.5) Andre' -- Those who desire to give up Free

[PATCH] make LyXText::status understandable ...

2003-03-13 Thread John Levon
n 1.288 diff -u -p -r1.288 text2.C --- text2.C 13 Mar 2003 21:19:01 - 1.288 +++ text2.C 13 Mar 2003 22:21:58 - @@ -2465,30 +2465,31 @@ LyXText::text_status LyXText::status() c } -void LyXText::status(BufferView * bview, LyXText::text_status st) const +void LyXText::st

Re: LyXText::status

2003-03-13 Thread John Levon
On Thu, Mar 13, 2003 at 09:59:34PM +, John Levon wrote: > >2482 if (status_ != NEED_MORE_REFRESH || st != NEED_VERY_LITTLE_REFRESH) { OK OK I can't read. Sorry for the noice john

LyXText::status

2003-03-13 Thread John Levon
2482 if (status_ != NEED_MORE_REFRESH || st != NEED_VERY_LITTLE_REFRESH) { Umm. I guess I'll fix this so it reflects what the comment says rather than the nonsensical code. john

LyXText->status

2002-08-01 Thread John Levon
2638 // We should only go up with refreshing code so this means that if 2639 // we have a MORE refresh we should never set it to LITTLE if we still 2640 // didn't handle it (and then it will be UNCHANGED. Now as long as 2641 // we stay inside one LyXTex