The QofQuery param_list is a GSList of const char*. Every SCM Query
would typically leak the GSList. This change will store the params
into the string cache, and the cached string is passed onto the
QofQuery param.
strptime will reasonable return false for an incomplete date but it
still fills in the parts of the struct tm that it understands, so bail
out of qof_scan_date_internal when it fails only if all three fields
are present.
There is a conflict when updating the tooltip menu entries for the
scheduled transaction 'edit' menu. To find the appropriate menu entry,
the list of menu entries is searched by name and this entry conflicts
with the main 'edit' menu which has no tooltip and so the scheduled
'edit' menu entry does not get the correct tooltip.
To fix this just change the entries to 'Edit Schedule'/'New Schedule'
and 'Delete Schedule', this also changes them to the same format as the
account menu options.
If you have a highlighted SX and you right click on another SX the new,
edit, delete popup uses the highlighted SX not the one you clicked on.
This is misleading because the box appears at the right clicked
location, and it looks like that is the SX it will affect.
To fix this, check to see if SX right clicked on is selected, if not
unselect all SX's and select the one clicked on before popup.
When you enter a value in the SLR tree view, the cell renderer text
entry box gets the focus ready for keyboard entry. In this state, the
tree view can be scrolled underneath by the mouse wheel or using the
vertical scrollbar, the row is still high lighted but still may be
confusing.
This commit disables the scrolling while an entry has focus and also
disables the horizontal scroll bar to be more effective.
If the scheduled transaction state is 'Reminder' and also requires
values which have been entered but the state has not been changed to
'To Create' the values are lost when OK button pressed.
This change adds a check of state to the 'variable_value_changed_cb'
and if 'Reminder' changes it to 'To Create'.
When in the SLR dialog and you are adding a value to a scheduled
transaction, if you do not complete the entry with a tab or enter but
press the 'OK' button the value changes back to 'Need Value'.
This change also completes the entry with the 'OK' button and will move
to the next value to be entered or if none complete the dialog.
Use csv_tximp_preview_sep_button_cb solely as a callback, its error
handling doesn't make sense otherwise. All we want at the end of
preview_refresh is to attempt a tokenize.
In addition to not going into an infinite loop with the message box
this presents a more helpful message suggesting that the encoding is
wrong.
As the tree view is based on the GNC_TREE_VIEW, if the pref_name of a
column is "name" it should also be the default sort column. This is
because the default column for GNC_TREE_VIEW is "name" and when saving
state information, 'gnc_tree_view_save_state' will only save non
default values where possible.
In this case if the name column is selected to be default, no entries
are saved in the gcm file and hence the on next load 'next occurrence'
will be used as the default.
Because acting on the date format selection was in the skipped
gnc_ui_qif_import_account_prepare. Move the action to
gnc_ui_qif_import_date_valid_cb so that it's done every time the date
format page is visited.
Previously, GnuCash would include only a single split's amount as the check
amount. If a "bank" account has multiple subaccounts for budgeting reasons, and
a transaction involves both "internal" (e.g. from one bank subaccount to
another bank subaccount) and external transfers, then even when a "subaccount"
register showing the top-level bank account is printed from, the check will
have the amount of the first split rather than the total of all splits which
are from subaccounts.
This change communicates the parent account (when viewed from a "subccount"
register) to the check printing dialog so that the check amount matches the
amount displayed in the register.
