Re: [Development] Splitting Qt Network out of qtbase (was: QtBase network failures)

2022-06-26 Thread Thiago Macieira
On Sunday, 26 June 2022 06:38:30 PDT Volker Hilsheimer wrote: > (*) As for the UNC stuff - it seems that we are testing only string parsing > code. We are not taking care of any of the actual network traffic or SMB > protocol. So do we need to access a share from a remote server at all? > Would it

Re: [Development] Splitting Qt Network out of qtbase (was: QtBase network failures)

2022-06-26 Thread Volker Hilsheimer
> On 25 Jun 2022, at 18:33, Thiago Macieira wrote: > > On Saturday, 25 June 2022 01:57:24 PDT Volker Hilsheimer wrote: >> Perhaps this is a good time to discuss whether we should move Qt Network >> into its own repository. This would make qtbase integrations less exposed >> to network failure,

Re: [Development] "*|All Files" as filter for QFileDialog

2022-06-26 Thread Marius P
> filter syntax than Qt (where I don’t think it’s ever been anything else than what it is today). If this is the answer to my question. Then I vote: * A developer would expect to see QFileDialog used with a filter that respects the Qt documentation, e.g. "". Instead of a filter that does not respe

Re: [Development] "*|All Files" as filter for QFileDialog

2022-06-26 Thread Volker Hilsheimer
> On 26 Jun 2022, at 02:28, Marius P wrote: > > Hello, > > From what I can see, "*|All Files" does not work as filter for QFileDialog if > using the Qt file open dialog, not the KDE file open dialog. I am on Kubuntu > 22.04. The file open dialog says that I have zero files in the directory. >