Re: [Development] QML Rectangle corner radius API for Qt 6.7

[Mike Trahearn via Development]

To Volker's point: I also mentioned in my post that Qt Quick never had a 
Triangle. Or Circle. Or any other primitive shapes. It has come up before that 
the use of ShapePath is one solution for such cases, but that also it isn't the 
most performant.
To that end I would recommend this thread focus on the tidying up of the so 
called "radiii" properties and close it off as a finished convenience so 
long as backwards compatibility is kept and property assignments make sense 
(e.g. clamping).

My other point was the interaction with the existing radius property - nobody 
has yet mentioned that Rectangle has always had a radius (so we can make a 
circle!).
Taking a lesson from QtQuick.Controls, the padding property is considered a 
"shortcut" to setting four other sub properties (which, by the way, don't have 
a group - and nobody complains... Matthias point was not to introduce another 
QObject to every Rectangle))
The padding property is this ignored if one of the sub properties are set. I'm 
assuming that negative values are handled well in this case. A negative radius 
might simple give you knobbles instead - like the rounded corners of a flight 
case.
Setting the existing radius property would become a shortcut to setting all the 
other four if not set (internally) such that they behave well together like the 
padding on a control.

Btw the fill of the proposed asymmetrical radiused rectangle appears to be 
correct from the images in Matthias' post so I don't think that is an issue.


From: Development  on behalf of Lars Knoll 
via Development 
Sent: Saturday, December 23, 2023 3:40:32 AM
To: Giuseppe D'Angelo 
Cc: development@qt-project.org 
Subject: Re: [Development] QML Rectangle corner radius API for Qt 6.7

> On 22 Dec 2023, at 17:48, Giuseppe D'Angelo via Development 
>  wrote:
>
> Il 22/12/23 17:08, Pierre-Yves Siret ha scritto:
>> I wouldn't want a radii grouped property just because of its name.
>> I much prefer writing topLeftRadius: 10 than radii.topLeft: 10.
>> The pedantic latin syntax doesn't help with the readability. Maybe that's 
>> just because I am not a native English speaker.
>
>
> It might be pedantic, but here's an excerpt from the docs:
>
>> Individual corner **radii** can be set as well (see below).
>
>
> Anyhow, something like:
>
>  borderRadius: { topLeft: 10; bottomRight: 10 }
>
> (or cornerRadius or whatever) fixes the API issue I was mentioning, it's 
> discoverable, it's "obvious", has minimal impact (1 property on Rectangle 
> instead of 4), and it's also compact to write.

Yes, that’s what I had in mind.

Naming wise I would vote for borderRadius, simply because that name and its 
behaviour is well known for most developers and designers from CSS. 
cornerRadius could be an alternative (I think Figma uses that name).

Cheers,
Lars
--
Development mailing list
Development@qt-project.org
https://urldefense.com/v3/__https://lists.qt-project.org/listinfo/development__;!!Nbma_1s!phv0VmW2IryOl2G3D2VdsNkqbiOPt05vEJJGhE7gqcPUpal7mxAHB0cXEPsNgE1rvjgbKWeQG6mNX1vDZIkZnWhf7g$
Confidentiality Notice: This message (including attachments) is a private 
communication solely for use of the intended recipient(s). If you are not the 
intended recipient(s) or believe you received this message in error, notify the 
sender immediately and then delete this message. Any other use, retention, 
dissemination or copying is prohibited and may be a violation of law, including 
the Electronic Communication Privacy Act of 1986.   ­­
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QML Rectangle corner radius API for Qt 6.7

[Lars Knoll via Development]

> On 22 Dec 2023, at 17:48, Giuseppe D'Angelo via Development 
>  wrote:
> 
> Il 22/12/23 17:08, Pierre-Yves Siret ha scritto:
>> I wouldn't want a radii grouped property just because of its name.
>> I much prefer writing topLeftRadius: 10 than radii.topLeft: 10.
>> The pedantic latin syntax doesn't help with the readability. Maybe that's 
>> just because I am not a native English speaker.
> 
> 
> It might be pedantic, but here's an excerpt from the docs:
> 
>> Individual corner **radii** can be set as well (see below).
> 
> 
> Anyhow, something like:
> 
>  borderRadius: { topLeft: 10; bottomRight: 10 }
> 
> (or cornerRadius or whatever) fixes the API issue I was mentioning, it's 
> discoverable, it's "obvious", has minimal impact (1 property on Rectangle 
> instead of 4), and it's also compact to write.

Yes, that’s what I had in mind. 

Naming wise I would vote for borderRadius, simply because that name and its 
behaviour is well known for most developers and designers from CSS. 
cornerRadius could be an alternative (I think Figma uses that name).

Cheers,
Lars
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QML Rectangle corner radius API for Qt 6.7

[Giuseppe D'Angelo via Development]

Il 22/12/23 17:08, Pierre-Yves Siret ha scritto:


I wouldn't want a radii grouped property just because of its name.
I much prefer writing topLeftRadius: 10 than radii.topLeft: 10.
The pedantic latin syntax doesn't help with the readability. Maybe 
that's just because I am not a native English speaker.





It might be pedantic, but here's an excerpt from the docs:


Individual corner **radii** can be set as well (see below).



Anyhow, something like:

  borderRadius: { topLeft: 10; bottomRight: 10 }

(or cornerRadius or whatever) fixes the API issue I was mentioning, it's 
discoverable, it's "obvious", has minimal impact (1 property on 
Rectangle instead of 4), and it's also compact to write.


My 2 c,
--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - Trusted Software Excellence



smime.p7s
Description: Firma crittografica S/MIME
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QML Rectangle corner radius API for Qt 6.7

[Pierre-Yves Siret]

Le ven. 22 déc. 2023 à 14:19, André Somers  a
écrit :

> The point I wanted to raise was that having four separate properties isn't
> ideal, and that we could give ourselves a lot of room for improvement by
> having a `corners` grouped property that can contain more than just a
> single real value for a radius.
>

I think that's a valid point but the alternatives are not worth it.
The anchors grouped property is nice to use and it has 17 sub-properties
that make sense and sensible names.

I wouldn't want a radii grouped property just because of its name.
I much prefer writing topLeftRadius: 10 than radii.topLeft: 10.
The pedantic latin syntax doesn't help with the readability. Maybe that's
just because I am not a native English speaker.

Changing radius to be grouped is not possible due to backward
compatibility, and I am not even sure it would be a reasonable API break
for Qt 7.

You mentioned a corners grouped property. What would be the syntax?
corners.topLeft: 10 ? This isn't descriptive enough.
corners.topLeft.radius: 10 ? That's a bit of a mouthful.
It realistically won't have other properties than radius. Specifying a
color for each corner seems very niche. Having the ability to change the
color of a side seems more useful and we don't even have that, not that it
is a big deal.
Do you have other properties in mind?
Mike's suggestion on LinkedIn about bevels is more sensible but has he said
it's a bit of a feature creep.
After a quick look, I don't see any feature requests for additional corner
properties in Jira.

The issue reported by Kai is worth fixing though.

Using BorderImage or implementing your own custom Rectangle if you want
more control seems to be better than overly complexifying the Rectangle API.

Pierre-Yves
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QML Rectangle corner radius API for Qt 6.7

[Volker Hilsheimer via Development]

> On 22 Dec 2023, at 13:59, Lars Knoll via Development 
>  wrote:
> 
>> 
>> On 22 Dec 2023, at 13:54, Tor Arne Vestbø via Development 
>>  wrote:
>> 
>>> On 22 Dec 2023, at 13:20, Giuseppe D'Angelo via Development 
>>>  wrote:
>>> 
>>> Il 22/12/23 11:15, André Somers ha scritto:
 I can see two options. The simplest option is to have a `radii`
 property, which is a grouped property containing the `topLeft`,
 `topRight`, `bottomLeft` and `bottomRight` properties as a floating
 point value as we have now. I think that would be cleaner than the
 current state of things.
>>> 
>>> While at it, it should be aptly named `cornersRadii` or similar.
>>> 
>>> `radius` has always violated Qt API guidelines. A rectangle doesn't have a 
>>> radius. We shouldn't be doing the same mistake again.
>> 
>> Radius is a well established term for this in Qt, and other UI frameworks. A 
>> key principle in Qt’s API design is familiarity and consistency.
> 
> I’m not 100% sure about this. “Radius" without any pre/postfix is IMO 
> somewhat confusing on a rectangle. HTML uses “borderRadius”, which I actually 
> like quite a bit. And as it’s a new property, it would also not cause 
> conflicts with the old name.
> 
> Cheers,
> Lars



CSS has https://developer.mozilla.org/en-US/docs/Web/CSS/border-radius

plus the per-corner values, e.g. 
https://developer.mozilla.org/en-US/docs/Web/CSS/border-top-left-radius

That is not specific to a rectangle though, and “border” is a well-defined CSS 
concept, so I’m not quite convinced that a rectangle’s “borderTopLeftRadius” 
makes sense. What happens to the fill?


We have “Rectangle.radius" today already, and we cannot/should not overload 
properties (radius as either holding a real, or a gadget type).

QPainter::drawRoundedRect [1] has parameters xRadius, yRadius, so evidently 
there are use cases for customizing the rounding of corners beyond a single 
value.

[1] https://doc.qt.io/qt-6/qpainter.html#drawRoundedRect

Making the whole thing into a grouped property would be nice indeed, but if we 
want to make it extensible, then “cornerProperties” is perhaps an option. That 
allows us to have all sorts of values for each corner, and the question becomes 
at some point whether we are over-engineering the simple concept of a rectangle.

Volker

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QML Rectangle corner radius API for Qt 6.7

[André Somers]

On 22-12-2023 14:12, Tor Arne Vestbø wrote:




On 22 Dec 2023, at 13:59, André Somers  wrote:

And what type would the radius property return then? I guess it would 
have to be the grouped type. But that would break all code that 
currently creates a binding on radius expecting it to be a real.


True, that would not work too well. The grouped type would need to be 
convertible to a qreal I guess?


What does `radius` return today, with the new API, when you’ve set 
only topLeftRadius?


It returns what it always did: a real with value 0.

The new API that is introduced in Qt 6.7 as it stands now just makes 
that value act as the /default/ value for the more specific radii 
properties. I think that that is sound design: it's backwards compatible 
and consistent with things like anchors.margins providing the default 
for the more specific margins (except for the fact that that property is 
spelled margins (plural) while radius is singular.)


Anyway, I think that this is besides the point. The point I wanted to 
raise was that having four separate properties isn't ideal, and that we 
could give ourselves a lot of room for improvement by having a `corners` 
grouped property that can contain more than just a single real value for 
a radius.


André
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QML Rectangle corner radius API for Qt 6.7

[Tor Arne Vestbø via Development]

On 22 Dec 2023, at 13:59, André Somers  wrote:


And what type would the radius property return then? I guess it would have to 
be the grouped type. But that would break all code that currently creates a 
binding on radius expecting it to be a real.

True, that would not work too well. The grouped type would need to be 
convertible to a qreal I guess?

What does `radius` return today, with the new API, when you’ve set only 
topLeftRadius?

Tor Arne



-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QML Rectangle corner radius API for Qt 6.7

[kde]

Hi,

my biggest gripe is actually the fact that -1 denotes "no specific radius".

Right now if you assign a negative radius it will effectively clamp to zero, so 
you can easily assign radius: magicValue - otherValue without worrying about it 
doing weird things. Or use an animation on it.

With the new radius properties if you assign -2 it will complain and set it to 
zero, if you assign -1 it will reset to "global radius" and if you set it to 0 
it will mean "explicitly no radius on this corner".

I've tried addressing this myself but Rectangle itself doesn't actually enforce 
any of this, it just forwards to simple rectangle node which also has this 
behavior baked in.

I believe only setting it to undefined (property RESET) should revert to global 
radius, not any magic number value.

FTR I filed this as https://bugreports.qt.io/browse/QTBUG-120188

Cheers
Kai Uwe
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QML Rectangle corner radius API for Qt 6.7

[Tor Arne Vestbø via Development]

On 22 Dec 2023, at 13:59, Lars Knoll  wrote:

You don't often get email from l...@knoll.priv.no. 
Learn why this is important

On 22 Dec 2023, at 13:54, Tor Arne Vestbø via Development 
 wrote:

On 22 Dec 2023, at 13:20, Giuseppe D'Angelo via Development 
 wrote:

Il 22/12/23 11:15, André Somers ha scritto:
I can see two options. The simplest option is to have a `radii`
property, which is a grouped property containing the `topLeft`,
`topRight`, `bottomLeft` and `bottomRight` properties as a floating
point value as we have now. I think that would be cleaner than the
current state of things.

While at it, it should be aptly named `cornersRadii` or similar.

`radius` has always violated Qt API guidelines. A rectangle doesn't have a 
radius. We shouldn't be doing the same mistake again.

Radius is a well established term for this in Qt, and other UI frameworks. A 
key principle in Qt’s API design is familiarity and consistency.

I’m not 100% sure about this. “Radius" without any pre/postfix is IMO somewhat 
confusing on a rectangle. HTML uses “borderRadius”, which I actually like quite 
a bit. And as it’s a new property, it would also not cause conflicts with the 
old name.

It’s not only affecting the border though, which can be a bit confusing 
perhaps? https://developer.mozilla.org/en-US/docs/Web/CSS/border-radius has an 
explicit note of that: "The radius applies to the whole background, even if the 
element has no border;”.

Tor Arne
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QML Rectangle corner radius API for Qt 6.7

[Lars Knoll via Development]

> On 22 Dec 2023, at 13:54, Tor Arne Vestbø via Development 
>  wrote:
> 
>> On 22 Dec 2023, at 13:20, Giuseppe D'Angelo via Development 
>>  wrote:
>> 
>> Il 22/12/23 11:15, André Somers ha scritto:
>>> I can see two options. The simplest option is to have a `radii`
>>> property, which is a grouped property containing the `topLeft`,
>>> `topRight`, `bottomLeft` and `bottomRight` properties as a floating
>>> point value as we have now. I think that would be cleaner than the
>>> current state of things.
>> 
>> While at it, it should be aptly named `cornersRadii` or similar.
>> 
>> `radius` has always violated Qt API guidelines. A rectangle doesn't have a 
>> radius. We shouldn't be doing the same mistake again.
> 
> Radius is a well established term for this in Qt, and other UI frameworks. A 
> key principle in Qt’s API design is familiarity and consistency.

I’m not 100% sure about this. “Radius" without any pre/postfix is IMO somewhat 
confusing on a rectangle. HTML uses “borderRadius”, which I actually like quite 
a bit. And as it’s a new property, it would also not cause conflicts with the 
old name.

Cheers,
Lars

> 
> We can change the `radius` property from a qreal into a group property with 
> left/rigth/top/bottom, similar to anchors. We can detect in the setRadius 
> setter if the incoming argument is a real, and apply that to all of the 
> corners. That would be backwards compatible, and give a more granular API for 
> those that need it.
> 
> Tor Arne 
> 
> -- 
> Development mailing list
> Development@qt-project.org 
> https://lists.qt-project.org/listinfo/development

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QML Rectangle corner radius API for Qt 6.7

[André Somers]

On 22-12-2023 13:54, Tor Arne Vestbø via Development wrote:



On 22 Dec 2023, at 13:20, Giuseppe D'Angelo via 
Development  wrote:

Il 22/12/23 11:15, André Somers ha scritto:

I can see two options. The simplest option is to have a `radii`
property, which is a grouped property containing the `topLeft`,
`topRight`, `bottomLeft` and `bottomRight` properties as a floating
point value as we have now. I think that would be cleaner than the
current state of things.

While at it, it should be aptly named `cornersRadii` or similar.

`radius` has always violated Qt API guidelines. A rectangle doesn't have a 
radius. We shouldn't be doing the same mistake again.

Radius is a well established term for this in Qt, and other UI frameworks. A 
key principle in Qt’s API design is familiarity and consistency.

We can change the `radius` property from a qreal into a group property with 
left/rigth/top/bottom, similar to anchors. We can detect in the setRadius 
setter if the incoming argument is a real, and apply that to all of the 
corners. That would be backwards compatible, and give a more granular API for 
those that need it.


And what type would the radius property return then? I guess it would 
have to be the grouped type. But that would break all code that 
currently creates a binding on radius expecting it to be a real.


André
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QML Rectangle corner radius API for Qt 6.7

[Tor Arne Vestbø via Development]

On 22 Dec 2023, at 13:54, Tor Arne Vestbø  wrote:

We can change the `radius` property from a qreal into a group property with 
left/rigth/top/bottom, similar to anchors. We can detect in the setRadius 
setter if the incoming argument is a real, and apply that to all of the 
corners. That would be backwards compatible, and give a more granular API for 
those that need it.

And by top/left/bottom/right I of course meant topRight, etc :)

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QML Rectangle corner radius API for Qt 6.7

[André Somers]

On 22-12-2023 13:20, Giuseppe D'Angelo via Development wrote:

Il 22/12/23 11:15, André Somers ha scritto:

I can see two options. The simplest option is to have a `radii`
property, which is a grouped property containing the `topLeft`,
`topRight`, `bottomLeft` and `bottomRight` properties as a floating
point value as we have now. I think that would be cleaner than the
current state of things.


While at it, it should be aptly named `cornersRadii` or similar.

`cornerRadii` in that case.


`radius` has always violated Qt API guidelines. A rectangle doesn't 
have a radius. We shouldn't be doing the same mistake again.




The second option is to actually allow for some more customization, and
have a `corners` property, where each corner again is named as in the
`radii` above, but would itself be a grouped property that could not
only contain `radius` but also `color` (and perhaps other properties in
the future*). Setting different colors for each of the corners would
allow for way more flexible gradients than what we have at the moment.


I'm not sure how this would look like in code, though?


In QML code? Something like this, I imagine:

```qml
Rectangle {
  id: textBalloon
  radius: 5
  color: palette.theirMessagePrimary
  corners.topLeft {
    radius: 10
    color: palette.theirMessageSecondary
  }
  // ... message content, whatever
}

```

André
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QML Rectangle corner radius API for Qt 6.7

[Tor Arne Vestbø via Development]

> On 22 Dec 2023, at 13:20, Giuseppe D'Angelo via Development 
>  wrote:
> 
> Il 22/12/23 11:15, André Somers ha scritto:
>> I can see two options. The simplest option is to have a `radii`
>> property, which is a grouped property containing the `topLeft`,
>> `topRight`, `bottomLeft` and `bottomRight` properties as a floating
>> point value as we have now. I think that would be cleaner than the
>> current state of things.
> 
> While at it, it should be aptly named `cornersRadii` or similar.
> 
> `radius` has always violated Qt API guidelines. A rectangle doesn't have a 
> radius. We shouldn't be doing the same mistake again.

Radius is a well established term for this in Qt, and other UI frameworks. A 
key principle in Qt’s API design is familiarity and consistency.

We can change the `radius` property from a qreal into a group property with 
left/rigth/top/bottom, similar to anchors. We can detect in the setRadius 
setter if the incoming argument is a real, and apply that to all of the 
corners. That would be backwards compatible, and give a more granular API for 
those that need it.

Tor Arne 

-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QML Rectangle corner radius API for Qt 6.7

[Giuseppe D'Angelo via Development]

Il 22/12/23 11:15, André Somers ha scritto:

I can see two options. The simplest option is to have a `radii`
property, which is a grouped property containing the `topLeft`,
`topRight`, `bottomLeft` and `bottomRight` properties as a floating
point value as we have now. I think that would be cleaner than the
current state of things.


While at it, it should be aptly named `cornersRadii` or similar.

`radius` has always violated Qt API guidelines. A rectangle doesn't have 
a radius. We shouldn't be doing the same mistake again.




The second option is to actually allow for some more customization, and
have a `corners` property, where each corner again is named as in the
`radii` above, but would itself be a grouped property that could not
only contain `radius` but also `color` (and perhaps other properties in
the future*). Setting different colors for each of the corners would
allow for way more flexible gradients than what we have at the moment.


I'm not sure how this would look like in code, though?


Thanks,

--
Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - Trusted Software Excellence



smime.p7s
Description: Firma crittografica S/MIME
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development

Re: [Development] QML Rectangle corner radius API for Qt 6.7

[Mike Trahearn via Development]

+1 for tidying up the API in the manner suggested.

But a welcome addition - thanks to Matthias Rauter.and Mitch Curtis - who I 
would be asking about the group properties in the first instance.
- which I already did 7 months ago...

https://www.linkedin.com/feed/update/urn:li:activity:7063432845276364800?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7063432845276364800%2C7064055958565515264%29=urn%3Ali%3Afsd_comment%3A%287064055958565515264%2Curn%3Ali%3Aactivity%3A7063432845276364800%29


From: Development  on behalf of André 
Somers 
Sent: Friday, December 22, 2023 8:15:52 PM
To: development@qt-project.org 
Subject: [Development] QML Rectangle corner radius API for Qt 6.7

Hi,

Starting from 6.7 we'll have separate corner radii for the corners of a
Rectangle. Nice, very welcome!

https://urldefense.com/v3/__https://doc-snapshots.qt.io/qt6-6.7/qml-qtquick-rectangle.html__;!!Nbma_1s!qEoiP92cqhsfnX-HHwEApg2oZPI0sCUo_e1WoYidXIlOByAeSXryFEIY7fgBhrVIkzA9_OzYV_e1XeHzfDE$

Unfortunately, the API looks a bit clunky and not ready for further
extension. Would it not be better to use a grouped property here instead
of having four different properties?

I can see two options. The simplest option is to have a `radii`
property, which is a grouped property containing the `topLeft`,
`topRight`, `bottomLeft` and `bottomRight` properties as a floating
point value as we have now. I think that would be cleaner than the
current state of things.

The second option is to actually allow for some more customization, and
have a `corners` property, where each corner again is named as in the
`radii` above, but would itself be a grouped property that could not
only contain `radius` but also `color` (and perhaps other properties in
the future*). Setting different colors for each of the corners would
allow for way more flexible gradients than what we have at the moment.

Cheers,

André

*) For instance, there could be properties that give even finer control
over the radius, so you can make an inverted rounded corner, or have
different radii for the x and y axis, or...


--
Development mailing list
Development@qt-project.org
https://urldefense.com/v3/__https://lists.qt-project.org/listinfo/development__;!!Nbma_1s!qEoiP92cqhsfnX-HHwEApg2oZPI0sCUo_e1WoYidXIlOByAeSXryFEIY7fgBhrVIkzA9_OzYV_e1rrag9_4$
Confidentiality Notice: This message (including attachments) is a private 
communication solely for use of the intended recipient(s). If you are not the 
intended recipient(s) or believe you received this message in error, notify the 
sender immediately and then delete this message. Any other use, retention, 
dissemination or copying is prohibited and may be a violation of law, including 
the Electronic Communication Privacy Act of 1986.   ­­
-- 
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development