2010/11/28 Michal <ms-li...@ms.sebdan.com>: > In this mail I've collected all the bugs with LyX 2.0beta1 I've > spotted so far. Overall, the experience has been very pleasant, but > there are some glitches worth correcting. My platform is (for now) Win > XP SP3 Polish. > > If something is unclear, please ask - I'm writing this in a hurry, > hoping that it will help developing LyX further anyway. > > Also, most of these bugs seems small to me. If the need arises, I > can file individual tickets, but I hope it won't be neccessary. > > [BUG #1] > Branch insets "override" all the rmb menus, so for example the user > cannot spellcheck single word inside the branch inset via rmb anymore. > This makes working with branches a whole lot harder.
This was bug http://www.lyx.org/trac/ticket/6642. Now fixed in r36604--r36609. > [BUG #2] > In LyX 1.6.x, after toggling particular branch from the document > properties, all the related insets were opened/closed. That was very > convenient and saved a lot of my time, as I'm using branches (sometimes > even nested ones) and heavily depend on these. This behaviour is no > longer present in LyX 2.0beta1. > > I'm not 100% sure whether it is a feature or a bug, but if it is > the former, maybe adding an option to rmb menu to "open all/close all" > insets of the particular branch would be useful instead? Fixed at r36610. > > [BUG #3] > I cannot add words with special (national) characters to the > personal dictionary - the request seems to be simply ignored by LyX. > This has been tested with the default aspell engine. This looks like bug: http://www.lyx.org/trac/ticket/7043. > > [BUG #4] > I'm not entirely sure, but isn't "private" dictionary cleaned after > restarting/reloading LyX? Considering the discussion on lyx-devel that > I've seen some time ago, this might be the result of some other > aspell-related bug. Indeed. > > [BUG #5] > The dotted line used to mark misspelled words is almost invisible > (under some conditions). Is the color/thickness of the line > configurable? > No, this is hardcoded. Under which conditions is it almost invisible ? I fixed the fact that the color was hardcoded in r36612. > [BUG #6] > Document settings cannot be reverted via "undo". Or is it by design? That might be by design. It's rather unwanted that settings are undone and the user doesn't see this happen. Vincent
