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
