Andre Poenitz wrote:
>> Note that rows are needed on setCursor only for setting the correct
>> bv->x_target (I think). I wonder if we can simply avoid that somehow.
>
> See attached.
Solved thanks.
Btw, the first rebreak after uncollapsing is wrong, but there are other
width problems so hopeful
On Wed, Jan 07, 2004 at 09:22:32AM +0100, Alfredo Braunstein wrote:
> Andre Poenitz wrote:
>
> > On Wed, Jan 07, 2004 at 09:07:24AM +0100, Andre' Poenitz wrote:
> >> The reason is probably that the row cache is empty as the row was never
> >> drawn.
> >>
> >> I am not sure how a proper solution w
On Wed, Jan 07, 2004 at 09:22:32AM +0100, Alfredo Braunstein wrote:
> Andre Poenitz wrote:
>
> > On Wed, Jan 07, 2004 at 09:07:24AM +0100, Andre' Poenitz wrote:
> >> The reason is probably that the row cache is empty as the row was never
> >> drawn.
> >>
> >> I am not sure how a proper solution w
Andre Poenitz wrote:
> On Wed, Jan 07, 2004 at 09:07:24AM +0100, Andre' Poenitz wrote:
>> The reason is probably that the row cache is empty as the row was never
>> drawn.
>>
>> I am not sure how a proper solution would look like.
>
> The attached patch paints over the problem...
;-)
Note that
On Wed, Jan 07, 2004 at 09:07:24AM +0100, Andre' Poenitz wrote:
> The reason is probably that the row cache is empty as the row was never
> drawn.
>
> I am not sure how a proper solution would look like.
The attached patch paints over the problem...
Andre'
Index: paragraph.C
On Wed, Jan 07, 2004 at 12:24:43AM +0100, Alfredo Braunstein wrote:
> open UG, click on first footnote ->
>
> #0 0x080ff99c in Row::pos() const ()
> #1 0x0811a765 in Paragraph::getRow(int) (this=0x83c7a88, pos=0)
> at ../../src/paragraph.C:1831
> #2 0x0813ef5d in LyXText::cursorX(LyXCursor
open UG, click on first footnote ->
#0 0x080ff99c in Row::pos() const ()
#1 0x0811a765 in Paragraph::getRow(int) (this=0x83c7a88, pos=0)
at ../../src/paragraph.C:1831
#2 0x0813ef5d in LyXText::cursorX(LyXCursor const&) const (this=0x8586eb4,
[EMAIL PROTECTED]) at ../../src/text.C:1873
Garst R. Reese wrote:
> Angus Leeming wrote:
>>
> No crash for me either selecting from menu or typing in the name.
> 1.4CVS from last night.
> xforms1.0
> gcc3.2
Try upgrading to include my latest commit. Of course, if you're using
anoncvs it might take some time to propogate through.
Meanwhi
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Friday 07 March 2003 1:41 pm, Lars Gullik Bjønnes wrote:
>> Angus Leeming <[EMAIL PROTECTED]> writes:
>> | Opening up the attached file causes LyX to crash.
>> | (gdb) r
>> | Starting program: /home/angus/lyx/devel/build-xforms/src/lyx
>> | [New Threa
On Friday 07 March 2003 1:41 pm, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
> | Opening up the attached file causes LyX to crash.
> | (gdb) r
> | Starting program: /home/angus/lyx/devel/build-xforms/src/lyx
> | [New Thread 8192 (LWP 26510)]
>
> This does not look as it i
Angus Leeming <[EMAIL PROTECTED]> writes:
| Opening up the attached file causes LyX to crash.
| (gdb) r
| Starting program: /home/angus/lyx/devel/build-xforms/src/lyx
| [New Thread 8192 (LWP 26510)]
This does not look as it is mine, but what where you doing?
Just loadning?
--
Lgb
Opening up the attached file causes LyX to crash.
(gdb) r
Starting program: /home/angus/lyx/devel/build-xforms/src/lyx
[New Thread 8192 (LWP 26510)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 8192 (LWP 26510)]
LyXView::updateLayoutChoice() (this=0xbfffe490)
at ..
12 matches
Mail list logo