Hi Trolls!
The documentation said that the Qt::MouseEventCreatedDoubleClick flag of
Qt::MouseEventFlags "Indicates that Qt has created a
MouseButtonDblClick event from this event. The flag is set in the
causing MouseButtonPress, and not in the resulting MouseButtonDblClick."
It is marked as "s
On Tuesday 10 March 2015 01:10:38 Arjun Das wrote:
> I tried to link the shell32.dll as follows in my .pro file :
>
> win32:LIBS += shell32.lib
win32: LIBS += -lshell32
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
>
> On Monday 09 March 2015 23:44:08 Arjun Das wrote:
> > *cpp.exe.2968.1625.jom qtmain.lib(qtmain_win.obj) : error LNK2019:
> > unresolved external symbol __imp__CommandLineToArgvW@8 referenced in
> > function _WinMain@16
>
> > I understand that this error is because of winmain function missing wh
On Monday 09 March 2015 23:44:08 Arjun Das wrote:
> *cpp.exe.2968.1625.jom qtmain.lib(qtmain_win.obj) : error LNK2019:
> unresolved external symbol __imp__CommandLineToArgvW@8 referenced in
> function _WinMain@16
> I understand that this error is because of winmain function missing which
> is req
Hi
I used the following configure options and commands to build qt5.5:
*configure -developer-build -opensource -confirm-license -platform
win32-msvc2013 -opengl desktop -nomake examples -nomake tests nmake*
QT is built successfully. After this, I installed QT creator 3.4.0 beta and
configured qm
On Mon, Mar 9, 2015 at 12:57 AM, Knoll Lars wrote:
> Yes, the best solution IMO is still to use your own malloc and operator
> new replacements. In addition, OOM handlers on the OS level can help.
Except that dynamically linked Windows Qt applications (read: most)
don't work this way, so Windows
> -Original Message-
> From: development-bounces+kai.koehne=theqtcompany.com@qt-
> [...]
> My problems are solved this way ,but i would rather like that qt takes care of
> this itself, meaning allowing setting warninglevel to 4 and warnings as errors
> and applications compile out of the
Well after some tests I learned that my original prolog is best. Adding #define QT_CC_WARNINGS
#include actually lead to warnings as is inlcuding a lot more than i thought. But this warnins are swicth off only later in the file.
There is not any benefit in my changes so i simplke removed them an
Hello,
we have an in-house policy to use warning level 4 and warnings-as-errors with our projects.
The problem is that qt headers are generating warnings when using this level.
We switch off some silly warnings like "unreferenced inline function has been removed", which are just informal and c
On Monday 09 March 2015 07:57:18 Knoll Lars wrote:
> The problem is that a non throwing new can’t reliably detect OOM issues.
> Even if we did check the return value of every 'operator new’ call in Qt,
> this would leave us with one big problem that’s more or less impossible to
> solve. The main pr
On 03/03/15 22:10, "Oswald Buddenhagen"
wrote:
>On Mon, Mar 02, 2015 at 10:11:33AM -0800, Thiago Macieira wrote:
>> On Monday 02 March 2015 11:21:10 Oswald Buddenhagen wrote:
>> > > I am actively against it while it's a huge burden on us for little
>> > > perceived benefit. You have to convince
On 07/03/15 04:03, "Thiago Macieira" wrote:
>On Friday 06 March 2015 17:42:00 Oswald Buddenhagen wrote:
>> 1) i'd like to propose the introduction of the code review score -3.
>
>> -1: "I would prefer this is not merged as is", advisory, non-sticky
>> -2: "This shall not be merged as is", blockin
12 matches
Mail list logo
