Every `arg(numeric_value)` overload uses a temporary `QString` object to build
a text representation of `numeric_value` needed by the actual
placeholder-replacement function. Even `arg(QChar)` and `arg(char)` create
single-character `QString`s and pass them to either `arg(const QString&)` or
`a
On Thursday, 5 March 2020 20:57:06 CET Benjamin TERRIER wrote:
> On Thu, 5 Mar 2020 at 19:56, Allan Sandfeld Jensen wrote:
> > Could you write it as a pac-script?
> >
> > I think there are some Chromium command-line arguments too that can change
> > the
> > defaults, but I think a pac-script is t
Den tors 5 mars 2020 kl 21:24 skrev Max Paperno :
>
> On 3/5/2020 3:11 PM, Elvis Stansvik wrote:
> > Den tors 5 mars 2020 kl 19:26 skrev Max Paperno :
> >> One thing for sure, since my benchmarks, from here on I will very much
> >> prefer the "multiArg" version of .arg() vs. using multiple .arg()s.
On 3/5/2020 3:11 PM, Elvis Stansvik wrote:
Den tors 5 mars 2020 kl 19:26 skrev Max Paperno :
One thing for sure, since my benchmarks, from here on I will very much
prefer the "multiArg" version of .arg() vs. using multiple .arg()s.
Closing side note: There's a a nice Clazy diagnostic for that.
Den tors 5 mars 2020 kl 19:26 skrev Max Paperno :
>
>
> On 3/5/2020 10:20 AM, Benjamin TERRIER wrote:
> >
> > I believe Marc was saying that using QStringLiteral *inside* a .arg()
> > call is an anti-pattern,
> > and not that using .arg() *on* a QStringLiteral is one.
> >
>
> Hmmm, good point, inde
On Thu, 5 Mar 2020 at 19:56, Allan Sandfeld Jensen wrote:
>
> Could you write it as a pac-script?
>
> I think there are some Chromium command-line arguments too that can change
> the
> defaults, but I think a pac-script is the most flexible and universal way.
>
>
This could be a solution. If PAC
On Wednesday, 4 March 2020 16:33:17 CET Benjamin TERRIER wrote:
> Hi,
>
> Is there any way to set a whitelist of URLs for proxy in Qt WebEngine?
>
> In Qt application this is done by implementing
> QNetworkProxyFactory::queryProxy() and returning NoProxy based on the query
> URL.
>
> However, ev
On 3/5/2020 10:20 AM, Benjamin TERRIER wrote:
I believe Marc was saying that using QStringLiteral *inside* a .arg()
call is an anti-pattern,
and not that using .arg() *on* a QStringLiteral is one.
Hmmm, good point, indeed it could be read that way. There are two
references to .arg() being
On Mon, 17 Feb 2020 at 05:33, Max Paperno wrote:
>
> Then found the [HEADS-UP: QStringLiteral][2] post by Marc on the
> development list and didn't feel so good about it anymore. Specifically
> where he says that using it with .arg() is an "anti-pattern" but not in
> any way that I can understand
