Hi all,
When did you tried that online installation?
Br,
Jani
> -Original Message-
> From: development-bounces+jani.heikkinen=digia@qt-project.org
> [mailto:development-bounces+jani.heikkinen=digia@qt-project.org]
> On Behalf Of Christian Gagneraud
> Sent: 5. helmikuuta 2014 4:03
Hi there,
I tried to install Qt with the latest official online installer on a
Windows computer [1], and I couldn't install it on the 'D' disk, because
the 'C' disk didn't have enough space to store the downloaded data (I
guess in the system temp dir, which is likely to be on c:)
Another annoy
On 2014-02-04 18:00, Matthew Woehlke wrote:
> (I might go with 'ifInvalid' though... )
Actually, I'll encourage defaultValue, for consistency with the
containers (unless those got renamed?).
> On 2014-02-04 17:06, Thiago Macieira wrote:
>> Em ter 04 fev 2014, às 16:04:11, Matthew Woehlke escreve
On 2014-02-04 17:06, Thiago Macieira wrote:
> Em ter 04 fev 2014, às 16:04:11, Matthew Woehlke escreveu:
>> If it were up to me, given an operator* (which is only one more
>> character of typing, after all), I wouldn't provide *any* (additional)
>> convenience access to the value. For roughly this
Le 04/02/2014 08:51, nic...@nicoladefilippo.it a écrit :
> Hi,
> put your file in android/assets directory and from qml:
>
> MediaPlayer {
> id: playMusic
> source: "assets:/example.mp3"
> }
>
Thanks, it works, next question, what is the proper way to manage a list
of sou
Em ter 04 fev 2014, às 16:04:11, Matthew Woehlke escreveu:
> If it were up to me, given an operator* (which is only one more
> character of typing, after all), I wouldn't provide *any* (additional)
> convenience access to the value. For roughly this reason; it's a lot of
> additional implementation
On 2014-02-04 15:07, Thiago Macieira wrote:
> Em ter 04 fev 2014, às 13:37:44, Matthew Woehlke escreveu:
>> Yeah, I'm not entirely on board with the whole "check the result or your
>> program dies" idea. Qt doesn't do that now; I definitely don't feel like
>> it needs to be added. (I guess QOptiona
On 2014-02-04 15:05, Tony Van Eerd wrote:
>> Yes, for QOptional you wouldn't want to name it 'isOkay()'. But you
>> *will* have the problem of ambiguous implicit conversion with
>> QOptional, which I assume will be allowed even if there is no
>> QString::toBool(). Alternatively you could omit impli
Em ter 04 fev 2014, às 13:37:44, Matthew Woehlke escreveu:
> > Sounds good, but should I then create a QExpected class? And how should I
> > make it differ from QOptional?
>
> I'm leaning more now toward having a separate (template) class for
> numeric conversions. I would strongly look into havin
>
> Yes, for QOptional you wouldn't want to name it 'isOkay()'. But you
> *will* have the problem of ambiguous implicit conversion with
> QOptional, which I assume will be allowed even if there is no
> QString::toBool(). Alternatively you could omit implicit value conversion
> entirely and require
On 2014-02-03 19:26, Thiago Macieira wrote:
> Em seg 03 fev 2014, às 15:29:06, Matthew Woehlke escreveu:
>> If I were designing such an API from scratch, I'd probably these days go
>> with something like the std::expected approach. Bonus points for
>> implicitly converting to the value type.
>>
>>
Em ter 04 fev 2014, às 09:49:54, Robert Knight escreveu:
> > I'll write QOptional tomorrow or on Wednesday, after I've had the chance
> > to read the proposal to C++14 (that was dropped).
>
> What would the plan for handling value access on unset options be?
> std::optional<>
> throws an exception
> I'll write QOptional tomorrow or on Wednesday, after I've had the chance
> to read the proposal to C++14 (that was dropped).
What would the plan for handling value access on unset options be?
std::optional<>
throws an exception. I initially did the same when implementing an
Optional class
but ra
This topic has never been formally closed. Since the discussion died down and
the topic has been agreed upon by consensus, we'd like to move forward testing
this scheme for a release and see if it works for Qt or not.
The people making the releases who mostly suffer under qt5.git not integrating
14 matches
Mail list logo
