Re: [Development] Playground Request: ClapInterface

2024-03-18 Thread Jean-Michaël Celerier
As someone involved in the audio ecosystem, the Clap plug-in API is quickly becoming an industry standard, is now supported by multiple digital audio workstation software (Reaper, Bitwig, qtractor) and a recurrent topic in audio conferences and circles. It has its own wikipedia page: https://en.wik

Re: [Development] Playground Request: ClapInterface

2024-03-18 Thread Volker Hilsheimer via Development
> On 18 Mar 2024, at 12:27, Dennis Oberst via Development > wrote: > > Hello all, > > I'd like to request a new playground repository to continue the development > of the "Clap Interface," a client-side library that uses QtGrpc to provide > integration with the CLAP audio plugin standard, ult

Re: [Development] On Removing Public Undocumented/\internal APIs

2024-03-18 Thread Volker Hilsheimer via Development
> On 13 Mar 2024, at 08:30, Marc Mutz via Development > wrote: > > TL;DR: Make qdoc openly document \internal members of documented > classes/namespaces or defined in public headers as "Internal. Subject to > change without notice. If you feel this function should be public, file > a bug repo

Re: [Development] Should QObject::event() be protected or public?

2024-03-18 Thread Volker Hilsheimer via Development
On 18 Mar 2024, at 14:00, Giuseppe D'Angelo via Development wrote: On 18/03/2024 13:34, André Somers wrote: While I know it's easy to work around, I sometimes find myself doing it anyway. To me, it signals what API is intended to be used in what way. That a class overrides `event` (or any other

Re: [Development] Should QObject::event() be protected or public?

2024-03-18 Thread Giuseppe D'Angelo via Development
On 18/03/2024 13:34, André Somers wrote: While I know it's easy to work around, I sometimes find myself doing it anyway. To me, it signals what API is intended to be used in what way. That a class overrides `event`  (or any other public virtual method) does not mean that that method is then inten

Re: [Development] Should QObject::event() be protected or public?

2024-03-18 Thread André Somers
Hey, On 18/03/2024 12:12, Giuseppe D'Angelo via Development wrote: Il 15/03/24 21:21, Jaroslaw Kobus via Development ha scritto: To the point: we are talking here about decreasing the visibility of a member function in a subclass. The virtuality of the method isn't relevant I guess, is it? It

Re: [Development] Should QObject::event() be protected or public?

2024-03-18 Thread Edward Welbourne via Development
Giuseppe D'Angelo (18 March 2024 12:12) > Therefore, when one creates a QObject subclass with an event() > override, then: > > * either they didn't know about the fact that it was public in > QObject, and thought it was protected/private (because virtual > functions should normally be protected

[Development] Playground Request: ClapInterface

2024-03-18 Thread Dennis Oberst via Development
Hello all, I'd like to request a new playground repository to continue the development of the "Clap Interface," a client-side library that uses QtGrpc to provide integration with the CLAP audio plugin standard, ultimately allowing to build audio plugins with Qt user interfaces. Description: Qt

Re: [Development] Should QObject::event() be protected or public?

2024-03-18 Thread Giuseppe D'Angelo via Development
Il 15/03/24 21:21, Jaroslaw Kobus via Development ha scritto: To the point: we are talking here about decreasing the visibility of a member function in a subclass. The virtuality of the method isn't relevant I guess, is it? It is relevant, since that's the whole problem: since event() is a vir