GitLab

BUG: 424745

(cherry picked from commit 820bda15)

In case the first processed split of a multi split transactoin matches
the filter criteria and no other one does, then the transaction was not
included in the report at all.

Since other splits may match the filter also, the first one found will
be stacked and only added, if no other data was added for that
transaction.

BUG: 424674

(cherry picked from commit 3a769f67)

In some cases, a provided category filter was ignored which caused no
filtering at all.

BUG: 424321
FIXED-IN: 5.1.1
(cherry picked from commit 910bc921)

When leaving an amount edit field in the new loan account wizard it will
automatically be filled with 0. This will prevent the loan calculator to
identify the field that should be calculated.

Enable the option to allow an empty field prevents the automatic fill
with the value 0 on focusOut event.

BUG: 424511

(cherry picked from commit 19e9ac50)

When an account name contains the less-than character followed by text,
that part is removed from the name in HTML based views (home view and
reports).

Escaping the less-than and greater-than characters to their HTML
equivalent solves the problem and all of the name is displayed.

BUG: 424188

(cherry picked from commit 5ce75274)

BUG: 424302

(cherry picked from commit 15947605)

The standard context menu of the webview object does not work in this
context so we simply suppress to show it.

BUG: 424305

(cherry picked from commit 637824bb)

Different sections of the home view displayed closed accounts depending
of the "Show all accounts" and "Do not show closed accounts"
differently. The handling has been harmonized such that closed accounts
will be displayed in all sections alike either if "Show all accounts" is
active or "Don't show closed accounts" is inactive.

Closed accounts will also be shown in strike-through so that they can
easily be identified as closed.

BUG: 424098

(cherry picked from commit 6e078d95)

The date picker object is used in other areas of KMyMoney (e.g.
transaction editor) where this problem does not show up. I analyzed it,
and the problem is, that the very first MouseReleaseButton event on the
date picker after object creation is not reaching the object under
unknown circumstances in the enter schedule dialog. This is not always,
but the scenario reported in the bug entry shows it. I have no idea
about the root cause, though.

Detecting the specific scenario and sending a mouse release button event
based on the data of the press event solves the problem. Drawback:
pressing the mouse long in that scenario now has no effect. It needs a
second press to get the number increasing while the mouse button is
pressed.

BUG: 424378

(cherry picked from commit fae59666)

(cherry picked from commit a64cba41)

BUG: 419275

(cherry picked from commit 84ff905e)

A few tags were incorrect since the last changes. This corrects it.

(cherry picked from commit 1ea0fe29)

AUTHOR: Antoni Bella Pérez <antonibella5@yahoo.com>

(cherry picked from commit 83656812)

(cherry picked from commit b54fbaa9)

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Shinjo Park authored May 25, 2020 and Thomas Baumgart committed Jun 29, 2020

Not all languages have numerals like English, so current English-centric
numeral rules do not fit everywhere. This allows scriptig of numeral
translations for more flexibility.

BUG: 413713
BUG: 420321

Shinjo Park authored May 24, 2020 and Thomas Baumgart committed Jun 29, 2020

Instead of joining strings directly, use placeholders for joining each
parts of numerals. This allows translators to change how numerals are
combining.

Separated the UI from the business logic for the template loader and
template writer. Added an item model for the templates and changed the
UI to use it.

Moved the template handling code into its own shared library.

This eliminates one of the cyclic dependencies between dialogs and
widgets.

Robert Szczesiak authored Jun 28, 2020 and Thomas Baumgart committed Jun 28, 2020

Signed-off-by: Robert Szczesiak <dev.rszczesiak@gmail.com>

In general, pressing the keypad's comma or dot character creates the
correct key press event for a locale. In case the keyboard option
"Four-level key with abstract separators" is set in the KDE settings,
the wrong character is used to create the event (e.g.: for locales DE or
FR a dot is returned when the decimal symbol is a comma).

This change fixes the problem such that a key press event for dot or
comma with the Qt::KeypadModifier set is turned into a key press event
with for the QLocale::decimalPoint() character.

(cherry picked from commit 2e0440ec)

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Since commit ab647428 the version extraction was broken. This commit
fixes the extraction to support the method introduced with the
aforementioned change.

(cherry picked from commit a3a14957)

Robert Szczesiak authored Jun 20, 2020 and Thomas Baumgart committed Jun 20, 2020

Constant reference parameter should be more efficient than copy.
Signed-off-by: Robert Szczesiak <dev.rszczesiak@gmail.com>

Resolved the static methods that did not work well in DLLs.

Robert Szczesiak authored Jun 19, 2020 and Thomas Baumgart committed Jun 19, 2020

Signed-off-by: Robert Szczesiak <dev.rszczesiak@gmail.com>