[digikam] [Bug 498218] Windows 10 crashes when Digikam is moved to secondary monitor

https://bugs.kde.org/show_bug.cgi?id=498218 --- Comment #3 from HubMiner --- I addressed the issue for myself - the primaty monitor was plugged into HDMI port corresponding to the CPU integrated GPU. Having both monitors plugged into NVidia removes the crash: it occurs when the window is moved

[digikam] [Bug 498218] Windows 10 crashes when Digikam is moved to secondary monitor

https://bugs.kde.org/show_bug.cgi?id=498218 --- Comment #2 from HubMiner --- Created attachment 177081 --> https://bugs.kde.org/attachment.cgi?id=177081&action=edit Misc Settings screen Tested as instructed, crashed again. -- You are receiving this mail because: You are watching

[digikam] [Bug 498218] New: Windows 10 crashes when Digikam is moved to secondary monitor

https://bugs.kde.org/show_bug.cgi?id=498218 Bug ID: 498218 Summary: Windows 10 crashes when Digikam is moved to secondary monitor Classification: Applications Product: digikam Version: 8.5.0 Platform: Other

[KOpeningHours] [Bug 448804] PH rule

https://bugs.kde.org/show_bug.cgi?id=448804 --- Comment #2 from HubMiner --- This helped me understand, thank you. I agree with "Su-Sa PH" -> "Su-Sa,PH" autoconversion, it seems a more likely guess over the current suggestion "PH Su-Sa closed". I started a

[KOpeningHours] [Bug 448804] New: PH rule

https://bugs.kde.org/show_bug.cgi?id=448804 Bug ID: 448804 Summary: PH rule Product: KOpeningHours Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR

[KOpeningHours] [Bug 447196] New: Incorrect range-combining when without days.

https://bugs.kde.org/show_bug.cgi?id=447196 Bug ID: 447196 Summary: Incorrect range-combining when without days. Product: KOpeningHours Version: unspecified Platform: Other OS: Other Status: REPORTED Sever

[KOpeningHours] [Bug 445785] Add correction for Russian statements

https://bugs.kde.org/show_bug.cgi?id=445785 --- Comment #11 from HubMiner --- As always, thank you for implementing this. Do you have a rough idea when this will be running in Osmose? -- You are receiving this mail because: You are watching all bug changes.

[KOpeningHours] [Bug 445963] weekday of the month

https://bugs.kde.org/show_bug.cgi?id=445963 --- Comment #3 from HubMiner --- A related issue, let me know if you want a separate submission: IN: Mon[1,3,-1] CURRENT: Mon[-1,1,3] DESIRED: input unchanged Why: negative numbers mean last or from the end. Humanly speaking, last should be after

[KOpeningHours] [Bug 445786] Remove all-days range

https://bugs.kde.org/show_bug.cgi?id=445786 --- Comment #2 from HubMiner --- Looks like we are going into human psychology with this topic. :) Based on my current OH correction experiences, I see many compound rules, for example: IN: Mo-Su 10:00-13:00; Mo-Su 14:00-20:00 OUT: Mo-Su 10:00-13

[KOpeningHours] [Bug 446135] Always open variations

https://bugs.kde.org/show_bug.cgi?id=446135 --- Comment #2 from HubMiner --- Technically, "open" as "sometimes open" disagrees with the documented meaning. This could be brought up in a wider forum, to get a range of opinions. Tools parsing "open" value wil