The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12627
==
Reported By:ngladitz
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12628
==
Reported By:Colin Powers
Assigned To:
On 12/13/2011 6:50 PM, Raphael Kubo da Costa wrote:
Qt has been LGPL-licensed for a few years, so the clause mentioning only
developers with a paid Qt license can change the code seems to be
outdated.
Applied, thanks:
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=470bcfad
-Brad
--
On Tuesday, December 13, 2011 04:51:16 pm Raphael Kubo da Costa wrote:
QKeySequence::Quit does not work on all platforms, and since it
translates to Ctrl+Q on all platforms where it does work, Ctrl+Q was
hardcoded instead.
---
Source/QtDialog/CMakeSetupDialog.cxx |2 ++
1 files changed,
Clinton Stimpson clin...@elemtech.com writes:
On Tuesday, December 13, 2011 04:51:16 pm Raphael Kubo da Costa wrote:
QKeySequence::Quit does not work on all platforms, and since it
translates to Ctrl+Q on all platforms where it does work, Ctrl+Q was
hardcoded instead.
---
On Thursday, December 15, 2011 08:20:14 am Raphael Kubo da Costa wrote:
Clinton Stimpson clin...@elemtech.com writes:
On Tuesday, December 13, 2011 04:51:16 pm Raphael Kubo da Costa wrote:
QKeySequence::Quit does not work on all platforms, and since it
translates to Ctrl+Q on all platforms
Alexander Neundorf wrote:
And, again a question regarding wording, currently the warnings generated
by automoc say Better do this and that for a more robust build.
I'd like to have a better way to express it.
Use this and that for STRICT mode compatibility. ?
or for qmake compatibility ?
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=12629
==
Reported By:Mark Abraham
Assigned To:
