And reset_version_info. This is a better solution than setting it in load
after calling init_version_info because in load it would over-write the
values stored in the database.
Fill in the gnucash and gnucash-resave versions in an initial load so
that the version checks pass. Have python's Session.__init__() always
load the session so it's ready to handle other actions.
The width of the columns in the totals view should be equal to the width in the
account view. Before this change, the values in the total column in the totals
view would move off the view to the right when resizing the left-most column.
Resizing the name column below two steps to the left:
| Name | Period 1 | Period 2 | ... | Total |
| Foo | 0 | 0 | ... | 0 |
------------------------------------------------
| Income | 0 | 0 | ... | 0 |
Resulted in this layout:
| Name | Period 1 | Period 2 | ... | Total |
| Foo | 0 | 0 | ... | 0 |
------------------------------------------------
| Income | 0 | 0 | ... | 0 |
- Settle for 'Saved report configuration' as name of the beast
in favour of 'Custom report' (ambiguous with full scheme reports added by the user)
or 'Saved report' (ambiguous with exported html reports)
or 'Preconfigured report' (which I personally like better but got criticisms)
- Group menu items related to saved report configurations together
in the Report menu
Set the GncDateEditor's time property, to which the GncPreference is bound.
If the property isn't set in a way that emits the "notify" signal the binding
doesn't know that it should change its value.
The way this is stored depends upon the SX End Date being invalid, but
xaccSchedXActionSetLastOccurDate() rejected invalid dates, so once a valid
date had been created, it was impossible to change, except to another valid
date.
This patch changes the decription column to allow long
text to be elipsizsed when column width is too narrow.
Also if the text is elipsized and the mouse is over
the text, a tooltip will appear with full text showing.
Profiling shows the main problem is checking the strings in the file for
valid XML and UTF-8. This does both in one pass, which cuts the time in
half, but it's still far slower than 2.4.x was.
Processing of DST information in Windows was utterly wrong. Fixed
that, including adding time resolution so that 00:00 on the day of
the change is recognized as being the old state.
