Hi,
I see that compiling Qt for wasm produces .a static libs.
This however leads to a couple of duplicate symbols when linking my existing
large application.
Here
https://emscripten.org/docs/compiling/Building-Projects.html?highlight=link#archive-a-files
I read
"Where possible it is better to ge
Hi,
You supposed to press the "Stage" button like before.
The greyed Submit button is kind of technically ok, but creates confusion
because it was previously hidden.
I created a task to Jira to hide it,
https://bugreports.qt.io/browse/QTQAINFRA-3245
--Jukka
_
Isn't it the stage one you want anyway as that puts it to CI etc.
Andy
-Opprinnelig melding-
Fra: Development på vegne av
"development@qt-project.org"
Organisasjon: KDAB
Svar til: Bogdan Vatra
Dato: tirsdag 1. oktober 2019 07:56
Til: "development@qt-project.org"
Emne: Re: [Developme
"Not that there's anything wrong with that." :-)
From: Development on behalf of Bogdan
Vatra via Development
Sent: Tuesday, October 1, 2019 7:53 AM
To: development@qt-project.org
Subject: Re: [Development] Gerrit update
Hi,
Since yesterday I can't su
Hi,
Since yesterday I can't submit any of my patches. The submit "button" is
gay, e.g. https://codereview.qt-project.org/c/qt/qtbase/+/273675
Am I doing something wrong?
Cheers,
BogDan.
În ziua de luni, 30 septembrie 2019, la 09:40:36 EEST, Heikki Halmet a scris:
> Hi,
>
> Coin fixed and i
On Mon, 30 Sep 2019 at 21:06, Matthew Woehlke wrote:
>
> On 30/09/2019 12.38, Ville Voutilainen wrote:
> > On Mon, 30 Sep 2019 at 19:12, Matthew Woehlke wrote:
> >>> QProperty fullname;
> >>> fullname.setBinding([&]() { return surname() + " " + lastname(); });
> >>
> >> I suppose this is c
On 30/09/2019 15.35, Thiago Macieira wrote:
> On Monday, 30 September 2019 11:06:18 PDT Matthew Woehlke wrote:
>> IOW, the example would look like:
>>
>>
>> fullname.setBinding(
>> [](Foo const* self){
>> return self->surname() + " " + self->lastname();
>> });
>
> How does the QPro
On Monday, 30 September 2019 11:06:18 PDT Matthew Woehlke wrote:
> IOW, the example would look like:
>
>
> fullname.setBinding(
> [](Foo const* self){
> return self->surname() + " " + self->lastname();
> });
How does the QProperty class know about Foo?
--
Thiago Macieira - thia
On 30/09/2019 12.38, Ville Voutilainen wrote:
> On Mon, 30 Sep 2019 at 19:12, Matthew Woehlke wrote:
>>> QProperty fullname;
>>> fullname.setBinding([&]() { return surname() + " " + lastname(); });
>>
>> I suppose this is convenient, but it also means creating a new function
>> object for *
On Mon, 30 Sep 2019 at 19:12, Matthew Woehlke wrote:
> > QProperty fullname;
> > fullname.setBinding([&]() { return surname() + " " + lastname(); });
>
> I suppose this is convenient, but it also means creating a new function
> object for *every instance of the type*. A more "traditional"
On 26/09/2019 11.02, Simon Hausmann wrote:
> I would like to propose an API that replaces the setter and getter
> functions on objects with a new property template class that
> encapsulates the property value instead, and the ability to tie
> binding expressions to these properties for automatic
On Donnerstag, 26. September 2019 20:46:15 CEST Lorn Potter wrote:
> Hi,
>
> On 26/9/19 3:57 PM, Martin Koller wrote:
> >> What configure line are you using? Are you trying to use -shared ?
> > ${QTDIR}/configure -xplatform wasm-emscripten -nomake examples \
> > -prefix ${dir}/qt5-installed -opens
On Donnerstag, 26. September 2019 20:46:15 CEST Lorn Potter wrote:
> Hi,
>
> On 26/9/19 3:57 PM, Martin Koller wrote:
> >> What configure line are you using? Are you trying to use -shared ?
> > ${QTDIR}/configure -xplatform wasm-emscripten -nomake examples \
> > -prefix ${dir}/qt5-installed -opens
On 26 Sep 2019, at 17:44, Simon Hausmann wrote:
>>> Yeah, custom setters are required.
>>>
>>> One option would be to say that such properties are implemented
>>> using the traditional property system altogether — bridging will be
>>> necessary anyway.
>>>
>>> Another option would be to implement
14 matches
Mail list logo
