self-explaining. Why don't we group them in two pairs: Section Up/Down, Level
Up/Down? The arrangement of the buttons may also give some hint to the user.
-- The correct list is not selected when right-clicking on a LOF or
+* The correct list is not selected when right-clicking on a LOF or
LOT inset.
-- When selecting a type which *is* already selected, the content in the
+* When selecting a type which *is* already selected, the content in the
browser window vanishes
-- The items in the treeview are editable
+* The items in the treeview are editable
-- When content (sections/captions) is changed, the toc/lof/lot is not properly
+* When content (sections/captions) is changed, the toc/lof/lot is not properly
updated.
MENUS
-* Special handling of [[...]] in text messages is disabled in messages.C
-
LAYOUT
visible toolbar, the modified settings are not considered for session management
REPLACED with a new entry, popup disabled (Peter 2006-11-09)
-
+
* Toolbars always show on the top of the screen, even though they are set to
"bottom" in the ui file (Joost 3/11/06).
-
+
FIXED: use the defaul.ui value only when there is no valid position stored
(1st start of lyx) (Peter 7/11/2006)
* Window positions are not remembered correctly. Each time a window is openend
window again it has moved towards the bottom of the screen. (Joost 3/11/06)
-
+
FIXED (Peter 8/11/2006)
+
+* Special handling of [[...]] in text messages is disabled in messages.C
+ FIXED (Georg 2006-11-12)
+
+* broken signal/slot connection:
+ Object::connect: No such signal LengthCombo::selectionChanged(LyXLength::UNIT)
+ Object::connect: (sender name: 'unitCO')
+ Object::connect: (receiver name: 'QVSpaceUi')
+ FIXED (JSpitzm 2006-11-12)