On Wed, 25 Apr 2012 15:03:21 ext Girish Ramakrishnan wrote:
> Hi Alan,
>
> On Wed, Apr 25, 2012 at 6:16 AM, wrote:
> >>From: ext Girish Ramakrishnan [gir...@forwardbias.in]
> >>Sent: Tuesday, April 24, 2012 12:50 PM
> >>To: Donald Carr
> >>Cc: Alpert Alan (Nokia-MP/Brisbane); development@qt-proj
My fault, it has been removed from QtCreator in July last year.
As Andreas said, qtpatch.cpp can be found in installer framework.
Debao
On Wed, Apr 25, 2012 at 5:46 PM, cat fa wrote:
>
>
> 在 2012年4月26日 上午1:20，1+1=2 写道：
>
>> In addition, a tool called qpatch is designed to do such a thing.
>>
>
On Wednesday 25 April 2012 14:40:27 lars.kn...@nokia.com wrote:
> On 4/25/12 3:11 PM, "ext Olivier Goffart" wrote:
> >On Wednesday 25 April 2012 13:47:35 Thiago Macieira wrote:
> >> However, I agree with you: it's too late to change it everywhere.
> >>
> >>Unless we
> >>
> >> do it properly, it al
On Wednesday 25 April 2012 15:07:24 Marc Mutz wrote:
> Hi Olivier,
>
> On Wednesday April 25 2012, Olivier Goffart wrote:
> > In Qt, we traditionally uses const reference as parameter for all our
> > setters. This is indeed probably the most efficient thing to do for
> > non-POD
> > in C++98 since
Also in the installer-framework, is something like that. And today I
pushed a fix to the operation, that will support Qt5.
Am 25.04.2012 19:20, schrieb 1+1=2:
> In addition, a tool called qpatch is designed to do such a thing.
>
> Qpatch 's source code can be found in QtCreator's repository.
>
>
In addition, a tool called qpatch is designed to do such a thing.
Qpatch 's source code can be found in QtCreator's repository.
src/tools/qpatch/qpatch.cpp
2012/4/25 Thiago Macieira :
> On quarta-feira, 25 de abril de 2012 18.50.01, Loaden wrote:
>> There have any way to modify (replace) the ha
On 4/25/12 5:01 PM, "ext Jordi Pujol" wrote:
>Hi all,
>
>I'm trying to embed a context-sensitive help system to my app. And I
>wonder why QtHelp module was left in the middle :-(
>
>I'll try to explain : you create your fancy-shiny-great-rich html/css
>based documentation ( doxygen or similar ) a
Hi all,
I'm trying to embed a context-sensitive help system to my app. And I
wonder why QtHelp module was left in the middle :-(
I'll try to explain : you create your fancy-shiny-great-rich html/css
based documentation ( doxygen or similar ) and you put it in a qch file.
Then, you want to use QH
On 4/25/12 3:11 PM, "ext Olivier Goffart" wrote:
>On Wednesday 25 April 2012 13:47:35 Thiago Macieira wrote:
>> However, I agree with you: it's too late to change it everywhere.
>>Unless we
>> do it properly, it also has the potential to make things worse. I'd
>>like to
>> ask you to find out whe
On 04/25/2012 02:44 PM, Thiago Macieira wrote:
> Ah, you're missing the trick!
Ah, I got it now, thanks! :-)
Ciao,
Alberto
--
http://blog.mardy.it <- geek in un lingua international!
___
Development mailing list
Development@qt-project.org
http://lis
On Wednesday 25 April 2012 13:47:35 Thiago Macieira wrote:
> However, I agree with you: it's too late to change it everywhere. Unless we
> do it properly, it also has the potential to make things worse. I'd like to
> ask you to find out where this is most important and do it now.
My point was to m
Hi Olivier,
On Wednesday April 25 2012, Olivier Goffart wrote:
> In Qt, we traditionally uses const reference as parameter for all our
> setters. This is indeed probably the most efficient thing to do for non-POD
> in C++98 since it avoids copy. But the situation is different in C++11
[...]
> We
On 25.4.2012 15.47, "alexandra.lei...@nokia.com"
wrote:
>On 25.4.2012 2:37 PM, "Mcdonald Jason (Nokia-MP/Brisbane)"
> wrote:
>
>>> I started a wiki page with a list of stuff to do with regards to Qt
>>> releases. It is based on our workflows from before and quite an
>>>efficient
>>> procedure.
On 25.4.2012 2:37 PM, "Mcdonald Jason (Nokia-MP/Brisbane)"
wrote:
>> I started a wiki page with a list of stuff to do with regards to Qt
>> releases. It is based on our workflows from before and quite an
>>efficient
>> procedure.
>>
>> http://qt-project.org/wiki/Release-procedure
>>
>> Please tak
On Apr 25, 2012, at 2:02 PM, ext Michael Jackson wrote:
OS X 10.6 only requires an intel processor. OS X 10.7 requires a 64 bit intel
processor.
http://support.apple.com/kb/SP575?viewlocale=en_US&locale=en_US
So if Qt 5 supports OS X 10.6 then Qt5 needs to be able to build in 32 bit mode.
Mi
> I started a wiki page with a list of stuff to do with regards to Qt
> releases. It is based on our workflows from before and quite an efficient
> procedure.
>
> http://qt-project.org/wiki/Release-procedure
>
> Please take a look and improve it as you see fit.
Do we need to co-ordinate with the C
On Wednesday 25 April 2012 13:57:31 Alberto Mardegan wrote:
> Hi Olivier,
>
> On 04/25/2012 01:12 PM, Olivier Goffart wrote:
> > The solution is actually much simpler:
> >
> > void Foo::setText(QString text) {
> >
> > d_ptr->text = std::move(text); // no copy
> >
> > }
> >
> > foo->setTex
On quarta-feira, 25 de abril de 2012 11.39.22, morten.sor...@nokia.com wrote:
> Yes, Qt 5.0 will support 32-bit builds. We'll have to figure out _how_. I'm
> not a big fan of multiple mkspecs so I'm going to suggest a configure
> option of some sort. Perhaps we can re-use "-device-option" from
> ht
On quarta-feira, 25 de abril de 2012 18.50.01, Loaden wrote:
> There have any way to modify (replace) the hard code paths built in
> QtCore5.dll ?
Just edit the binary file with a binary editor. You'll notice that the
variables have 512 bytes of space, so it should be enough to change it to
almos
On quarta-feira, 25 de abril de 2012 12.12.22, Olivier Goffart wrote:
> The problem is that this code might be slightly slower in some cases in
> C++98 due to the additional copy if qMove is not supported by the
> compiler. But the idea is that C++11 is going to be more widely adopted
> really soo
On quarta-feira, 25 de abril de 2012 13.57.31, Alberto Mardegan wrote:
> I understand why there wouldn't be a copy in the implementation of
> setText, but why wouldn't calling foo->setText() produce a copy?
> How can the compiler know that it must not create a copy when calling
> Foo::setText(QStri
On Apr 24, 2012, at 6:38 PM, ext Thiago Macieira wrote:
On terça-feira, 24 de abril de 2012 11.41.14, Stephen Chu wrote:
So I grabbed Qt 5 from git to give it a shot again. I am now more
confused then before. :)
The configure script uses pre-processor output from
qtbase/config.tets/arch/arch.cpp
Hi Olivier,
On 04/25/2012 01:12 PM, Olivier Goffart wrote:
> The solution is actually much simpler:
>
> void Foo::setText(QString text) {
> d_ptr->text = std::move(text); // no copy
> }
>
> foo->setText(tr("hello world")); // no copy here, this is a move.
I understand why there wouldn't
Hello!
I started a wiki page with a list of stuff to do with regards to Qt
releases. It is based on our workflows from before and quite an efficient
procedure.
http://qt-project.org/wiki/Release-procedure
Please take a look and improve it as you see fit.
Cheers,
Alexandra
--
Alexandra Leisse
W
As we know the qt paths is hard code
in qtbase\src\corelib\global\qconfig.cpp
My question:
There have any way to modify (replace) the hard code paths built in
QtCore5.dll ?
Thanks a lot!
static const char qt_configure_prefix_path_strs[][12 + 512] = {
> "qt_prfxpath=D:\\qpSOFT\\Projects\\Qt5\\
Hi,
In Qt, we traditionally uses const reference as parameter for all our setters.
This is indeed probably the most efficient thing to do for non-POD in C++98
since it avoids copy. But the situation is different in C++11
But first, some reminders of the cost of copies.
In Qt, most of our ob
26 matches
Mail list logo
