This project and board is for development tasks that do not require an API/ABI breakage.
Details
Thu, Apr 10
Wed, Apr 9
Mon, Apr 7
Thu, Apr 3
Wed, Apr 2
Mon, Mar 24
Mar 18 2025
Mar 15 2025
Mar 14 2025
Mar 13 2025
Mar 12 2025
Mar 5 2025
And created https://invent.kde.org/frameworks/kio/-/merge_requests/1828 for KF6
Could not think of any reason, so created a patch to approach the octet-stream default extension in another way, some autotest included;
https://invent.kde.org/frameworks/kio/-/merge_requests/1827
Sadly now for octet-stream if ,currentExtension emtpy then extension becomes bogus ".". Was there any reason to make the new option not still also depend on currentExtension (edi: being empty)?
Mar 4 2025
Feb 16 2025
Feb 6 2025
Jan 31 2025
Jan 30 2025
Jan 29 2025
May 9 2024
And now reported the challenge of drop objects lifetime vs user input on decisions by https://bugreports.qt.io/browse/QTBUG-125229
Hi. I just came across dropping random data (in my case an image) into file views not working, i.e. not creating any new files due to no more data in the QMimeData instance referred to in the DropJob.
Apr 6 2024
Sep 12 2023
Sep 1 2023
Aug 6 2023
Jul 31 2023
This is done now.
Jul 10 2023
- Replacement for Dialog is in progress
- Issues of FrameSvgItem are still valid on KSvg's FrameSgItem
Jul 9 2023
All of the usages are in Plasma, so we could move it there to avoid carrying it in Frameworks
Remaining:
Jun 28 2023
From a Frameworks POV this seems done.
Is there anything actionable or worth discussing here that wasn't addressed elsewhere?