On Thu, 24 Aug 2023 15:37:05 -0400
Eduardo Hopperdietzel wrote:
> Hi David,
>
> I've made a little Wayland app that uses both SHM and DMA, and I
> tested it on Weston, Sway, and my own compositor. I also tried it on
> three different machines: two with Intel i7 CPUs and one with a
> smaller ARM
On Thursday, 24 August 2023 05:37:28 PDT Volker Hilsheimer via Development
wrote:
> Before we now go on a campaign to clean all this up (as is already being
> reviewed for qstring.h), I’d rather evaluate other options for the existing
> code base.
>
> Can we disable this warning some in some
Hi David,
I've made a little Wayland app that uses both SHM and DMA, and I tested it
on Weston, Sway, and my own compositor. I also tried it on three different
machines: two with Intel i7 CPUs and one with a smaller ARM CPU. These
machines had Intel Iris Pro, Nvidia GT525M, and Mali-400 GPUs,
On Thursday, 24 August 2023 05:43:06 PDT Lars Knoll via Development wrote:
> I personally think it’s worthwhile discussing this and maybe
> modifying/easing our policies here to some degree.
Unfortunately, this decision is partially hardcoded in our plugin loading
mechanism: we only check the
On 24/08/2023 17:36, Volker Hilsheimer wrote:
On platforms where Qt is a system library, being able to at least launch your
application if the system has a lower patch level than what the binary was
built against sounds nice. But in practice, it’s rolling dice - the application
might work
> On 24 Aug 2023, at 14:43, Lars Knoll via Development
> wrote:
>
>
>> On 24 Aug 2023, at 14:30, Giuseppe D'Angelo via Development
>> wrote:
>>
>> On 22/08/2023 23:27, Marc Mutz via Development wrote:
>>> We have
>>>
> On 24 Aug 2023, at 14:30, Giuseppe D'Angelo via Development
> wrote:
>
> On 22/08/2023 23:27, Marc Mutz via Development wrote:
>> We have
>> https://community.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B
>> for backwards binary compatibility issues and we have
>>
Thanks for the background info, Cristian!
It’s fine to agree that, for new code, the inline goes only on the declaration,
and must not be on the definition.
For existing code: throwing the somewhat but not totally (I think) naive regexp
On 22/08/2023 23:27, Marc Mutz via Development wrote:
We have
https://community.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B
for backwards binary compatibility issues and we have
https://contribute.qt-project.org/quips/6 for acceptable and
unacceptable backwards source
Hi,
Which style are you referring to here?
The default QML one, none Fusion/Material/etc substyles.
If there's a way we can improve our desktop-based fallbacks, it would be good
to know about that.
First of all, they suffer from the same issue as most of QtQuick
Controls 2, being in the
On Wednesday, 23 August 2023 22:17:26 PDT Haowei Hsu wrote:
> However, if we currently can't improve windres.exe, is there another way to
> improve Qt itself?
Yes: don't put software in paths with spaces or other shell-special
characters. I've been fighting this problem while working on Qt for
11 matches
Mail list logo
