[kmymoney] [Bug 424378] Values of date picker runs out of control for scheduled payments and transactions
https://bugs.kde.org/show_bug.cgi?id=424378 --- Comment #7 from Thomas Baumgart --- *** Bug 430630 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424378] Values of date picker runs out of control for scheduled payments and transactions
https://bugs.kde.org/show_bug.cgi?id=424378 Ian Neal changed: What|Removed |Added CC||iann_bugzi...@blueyonder.co ||.uk --- Comment #6 from Ian Neal --- *** Bug 403335 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424378] Values of date picker runs out of control for scheduled payments and transactions
https://bugs.kde.org/show_bug.cgi?id=424378 Thomas Baumgart changed: What|Removed |Added Latest Commit|https://invent.kde.org/offi |https://invent.kde.org/offi |ce/kmymoney/commit/fae59666 |ce/kmymoney/commit/2731fc0e |c95c22ac68df3f347ba14c5e41a |2237d295e80d54e026c44b10110 |47f34 |a287a --- Comment #5 from Thomas Baumgart --- Git commit 2731fc0e2237d295e80d54e026c44b10110a287a by Thomas Baumgart. Committed on 19/07/2020 at 11:05. Pushed by tbaumgart into branch 'master'. Add missing release event in very specific case 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. (cherry picked from commit fae59666c95c22ac68df3f347ba14c5e41a47f34) M +26 -0kmymoney/widgets/kmymoneydateinput.cpp M +5-0kmymoney/widgets/kmymoneydateinput.h https://invent.kde.org/office/kmymoney/commit/2731fc0e2237d295e80d54e026c44b10110a287a -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424378] Values of date picker runs out of control for scheduled payments and transactions
https://bugs.kde.org/show_bug.cgi?id=424378 Thomas Baumgart changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/offi ||ce/kmymoney/commit/fae59666 ||c95c22ac68df3f347ba14c5e41a ||47f34 Resolution|--- |FIXED Version Fixed In||5.1.1 --- Comment #4 from Thomas Baumgart --- Git commit fae59666c95c22ac68df3f347ba14c5e41a47f34 by Thomas Baumgart. Committed on 19/07/2020 at 09:21. Pushed by tbaumgart into branch '5.1'. Add missing release event in very specific case 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. FIXED-IN: 5.1.1 M +26 -0kmymoney/widgets/kmymoneydateinput.cpp M +5-0kmymoney/widgets/kmymoneydateinput.h https://invent.kde.org/office/kmymoney/commit/fae59666c95c22ac68df3f347ba14c5e41a47f34 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424378] Values of date picker runs out of control for scheduled payments and transactions
https://bugs.kde.org/show_bug.cgi?id=424378 Thomas Baumgart changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from Thomas Baumgart --- This is weird: the date picker object is used in other areas (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. This is not always, but the scenario you have reported shows it. I have no idea about the root cause, though. So it's not related to flaky hardware or the date picker in general. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424378] Values of date picker runs out of control for scheduled payments and transactions
https://bugs.kde.org/show_bug.cgi?id=424378 --- Comment #2 from Jack --- I also wonder if you have check mouse click behavior in any scroll-bar, just to be sure it's not an issue with your mouse buttons sticking. Not likely, but easy enough to rule out. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 424378] Values of date picker runs out of control for scheduled payments and transactions
https://bugs.kde.org/show_bug.cgi?id=424378 --- Comment #1 from Jack --- Have you confirmed this is specific to the date part of the date picker? Have you tried it on the year or month? Have you tried using any other date picker in another app? (Just trying to be sure if this is specific to one widget or more general.) -- You are receiving this mail because: You are watching all bug changes.
