On Monday, 20 November 2023 10:39:54 PST Fabian Kosmale via Development wrote: > I am however a bit concerned about the timeline for the deprecation, and the > migration path we want to offer. There needs to be at least documentation > on how to properly port away form QSharedMemory, and maybe even a "new" > QSingleApplication (but one that doesn't use QSM in its implementation).
QtSingleApplication should use D-Bus where available. In fact, it should implement the KUniqueApplication API. Where not available, well, I actually don't know what its requirements are so I can't offer a suggestion. That said, deprecation should not be delayed. The bugs are there, right now. It shouldn't matter if we've fixed the code that is affected or not. As you can see from my change, I'm actually requesting it be backported to 6.6.1. > My suggestion would be that we > - discuss current QSM patterns, and how to move away from them > - based on that, create documentation and if necessary implement new classes > to help with the use cases - and only then deprecate QSharedMemory. I think we can delay the deprecation until we've had a chance to talk next week about whether we're going to have a replacement at all or not. If we're not, if the replacement is simply QFile, then there's nothing stopping us from deprecating. -- Thiago Macieira - thiago.macieira (AT) intel.com Cloud Software Architect - Intel DCAI Cloud Engineering
smime.p7s
Description: S/MIME cryptographic signature
-- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
