On Wed, 16 Aug 2000, Juergen Vigna wrote:
> With which version are you working? I'll see my work there terminated util
> I get some bugreports. So please could you give me more informations on the
> crashes and on the update-problems (ONLY if you are using the latest CVS).
I'm using latext CVS (i.e. the bug report is related to insettabular.C
rev. 1.44, Aug 11). I'll give a more detailed bug report in the following
lines:
The first table I inserted didn't redraw on resizing of the LyX
window. This changed after I inserted and deleted a few characters befoe
the table (in the same paragraph) - after that operation, it redraws fine.
The cursor doesn't only show up in editable places (the red boxes), but
also in the left and right edge of the table, where one can't insert
anything.
Cut/Copy/Paste of parts of the table doesn't work.
If your table isn't the first thing in the paragraph, but hangs out of the
visual space, and you move the cursor in a field beyond the LyX window,
the table moves over the text or whatever is before, and this text is
shining through (doesn't make editing that good).
The cursor inside a table is displayed a few pixels too high. That
increases in nested tables.
When I try to mark things in the table, the marking sections flickers
sometimes, and sometimes I even get a segfault. GDB tells me:
Program received signal SIGSEGV, Segmentation fault.
0x81f1c02 in InsetTabular::InsetButtonPress (this=0x837bd00, bv=0x831d040,
x=123, y=59, button=1) at insettabular.C:592
592 the_locking_inset->InsetButtonPress(bv, x-inset_x, y-inset_y, button);
(gdb) bt
#0 0x81f1c02 in InsetTabular::InsetButtonPress (this=0x837bd00,bv=0x831d040,
x=123, y=59, button=1) at insettabular.C:592
#1 0x81f977c in InsetText::InsetButtonPress (this=0x837ba7c, bv=0x831d040,
x=144, y=221, button=1) at insettext.C:587
#2 0x81f1ba7 in InsetTabular::InsetButtonPress (this=0x83799d8, bv=0x831d040,
x=258, y=221, button=1) at insettabular.C:584
#3 0x8058846 in BufferView::Pimpl::workAreaButtonPress (this=0x831d0f8,
xpos=258, ypos=221, button=1) at BufferView_pimpl.C:567
#4 0x80504ef in BufferView::workAreaButtonPress (this=0x831d040, xpos=304,
ypos=291, button=1) at BufferView.C:173
#5 0x8088f53 in WorkArea::work_area_handler (ob=0x831dfd8, event=2,
xev=0x400952ec) at WorkArea.C:298
#6 0x8088623 in C_WorkArea_work_area_handler (ob=0x831dfd8, event=2, key=1,
xev=0x400952ec) at WorkArea.C:49
#7 0x40059f83 in fl_handle_it () from /usr/X11R6/lib/libforms.so.0.88
#8 0x4005a029 in fl_handle_object () from /usr/X11R6/lib/libforms.so.0.88
#9 0x4004cfd1 in fl_handle_form () from /usr/X11R6/lib/libforms.so.0.88
#10 0x4004deb8 in do_interaction_step () from /usr/X11R6/lib/libforms.so.0.88
#11 0x4004dee2 in fl_treat_interaction_events ()
from /usr/X11R6/lib/libforms.so.0.88
#12 0x4004df1c in fl_check_forms () from /usr/X11R6/lib/libforms.so.0.88
#13 0x80f3f4d in LyXGUI::runTime (this=0x82f8f98) at lyx_gui.C:587
#14 0x80f60aa in LyX::LyX (this=0xbffff310, argc=0xbffff334, argv=0xbffff394)
---Type <return> to continue, or q <return> to quit---
at ../src/lyx_main.C:165
#15 0x813c613 in main (argc=2, argv=0xbffff394) at ../src/main.C:94
The following not really related to the table, that's the picture (created
with the picture button, is that the new graphics inset or the old one?):
If you change the file or the size, the surrounding inset is not
reformated properly (the cursor however moves as if it was). Also, after
startup, the "rendering image" is shown until you force some reformating.
Furthermore, LyX displays the inset bottom-aligned, while TeX renders it
top-aligned.
There are also strange formatting effects in paragraphs. E.g. if I merge
the paragraph with the table with the previous paragraph, the last word is
wrapped together with the table into a new line (that's ok). Now, if I
again put the table into a paragraph of it's own, the last word of the
previous paragraph stais where it is, an leaves the wide stretched line
before. This doesn't change unless you force some reformatting there.
Finally the vertical slider. It shrinks much faster than I expect. Well,
that's something that was in previous versions of LyX, too, and it's
probably related to xforms. In my GUI book, the size of the slider should
represent the fraction of the visible part of the document vs. the total
document (plus some minimal dimensions to keep it working for very large
documents).
I hope this bug report helps you to make LyX an even better tool than what
it is now!
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://www.jwdt.com/~paysan/
