On Mon, Nov 25, 2002 at 12:02:38AM +0100, Michael Schmitt wrote: > Some of the comments are very subjective. I apologize in advance if > anybody feels offended.
pshaw, we are tougher than that (or should be) > - Open "Save as..." -> Cancel -> Crash Can't see how this happens, but confirmed. Anyone ? > - To say the truth: I don't like the new xforms dialogs. I understand You must file individual bugs on *each* problem you see, or you won't be taken seriously... > - the NEWS file should list all new features (I couldn't find any > at first glance) We'll probably work on this nearer release > ==4284== Conditional jump or move depends on uninitialised value(s) > ==4284== at 0x81433B7: MathCursor::targetX() const (math_cursor.C:631) valgrind often has false positives, but they should at least be looked at > - When starting LyX: > > Received unhandled X11 event > Type: 13 Target: 0x260009c informational only really. xforms oddness > - When exiting LyX: > > ==4284== Invalid read of size 4 > ==4284== at 0x821A553: handle_bitmaptable (bmtable.c:217) > ==4284== by 0x82985F8: fl_handle_it (objects.c:1542) > ==4284== by 0x82988E4: fl_handle_object (objects.c:1572) > ==4284== by 0x82965B3: fl_free_object (objects.c:216) guess we free things in the wrong order. Angus ? > - The graphics dialog has been simplified which is a good thing. > However, I don't like to mix up "Scale" with "Width" - these I probably agree. It's a thorny problem > (even if it enlarges the dialog)! Moreover, it is not possible > to switch back to "Scale" once you have selected a width unit! please file bug ... > - Two comments on the paragraph dialog: If, e.g. "medskip" is selected, > a value entered in the field below should be grayed out. (Once again, > we can start an endless discussion on when a GUI is intuitive...) yes, file bug. > One of the oddities of LyX paragraphs are the "Above" and "Below" > settings. Can you tell me (without thinking) what comes first: the line or > the vertical space? Shouldn't lines and vertical spaces be provided > independently from paragraphs? This would also comply with the way LaTeX > handles them. I think you're probably right. The problem is how can we make copy/paste work sensibly with such a change, and how we store the info internally. This is probably a long-term thing (when we have a proper general DOM). > ==4432== Conditional jump or move depends on uninitialised value(s) > ==4432== at 0x80C5142: WriteAs(BufferView*, Buffer*, std::string const&) >(/usr/include/g++/bits/basic_string.h:338) > ==4432== by 0x80DA4F4: LyXFunc::dispatch(FuncRequest const&, bool) >(lyxfunc.C:963) > ==4432== by 0x80D9241: LyXFunc::dispatch(int, bool) >(/usr/include/g++/bits/basic_string.h:229) > ==4432== by 0x820EEAB: Menubar::Pimpl::MenuCallback(flobjs_*, long) >(../../../src/support/DebugStream.h:127) attach document in original form regards john -- Khendon's Law: If the same point is made twice by the same person, the thread is over.
