Hi,
This should go to qt-interest mail list instead of qt-development.
BTW, this error has nothing to do with CMAKE. and I couldn't understand
what you are trying to do with following code.
#ifndef Q_WS_WIN
return ((int*)(&Q_WS_WIN))[argc];
...
Regards,
Debao
On Tue, Mar 12, 2013 at 11:08
Hi, As far as I know, this is a bug of QtSDK installer for Qt4, you can
download latest Qt Library 4.8.X and Qt Creator manually.
https://code.google.com/p/qextserialport/wiki/qwineventnotifier_p_h
On Mon, Jan 21, 2013 at 7:41 PM, Sze Howe Koh wrote:
> On 21 January 2013 19:03, Labs, Torsten
Hi,
You should go to qt-interest instead of qt-development.
Regards,
Debao
On Tue, Dec 25, 2012 at 7:56 PM, Иван Комиссаров wrote:
> Sorry for offtop, but does anybody have sources for an example that was
> used to create this http://i.imgur.com/kn67x.png image? I want to have
> some pallett
Hi Randolph D,
Please note that, Qt libraries 5.0.0 for Windows only provided prebuild
version for MSVC2010 at present, if you using MSVC2005/2008/2012, you need
to compile it by yourself.
Once you have installed MSVC2010-express and Windows debug tools (cdb.exe),
you can using QtCreator to build
Hi,
I have commit a patch for this:
https://codereview.qt-project.org/#change,43312
Regards
Debao
On Fri, Dec 21, 2012 at 12:17 AM, Konstantin Ritt wrote:
> +1 to option 2
>
> Konstantin
>
>
> 2012/12/20 1+1=2 :
> > Hi all,
> >
> > At present, if we
Hi all,
At present, if we want to setting the Application Icon under Windows
platform, we should create a xxx.rc file first, then pass the file path to
qmake variable RC_FILE. see:
http://qt-project.org/doc/qt-5.0/qtdoc/appicon.html
I hope that we can directly specify the Application Icon throug
Maybe you can create a my.qdocconf.in file, then let qmake generating
proper my.qdocconf file for you.
On Wed, Nov 28, 2012 at 8:45 PM, Denis Shienkov wrote:
> Hello, Qt developers.
>
> Why not available Qt env variables from *.qdocconf file?
>
> For example,
>
> I need specify path to Qt Doc i
On Sat, Jun 9, 2012 at 1:54 AM, Thiago Macieira
wrote:
> On sábado, 9 de junho de 2012 01.42.21, 1+1=2 wrote:
>> > Do we need this for every file, or is one entry in qglobal.h enough?
>>
>> One entry in qglobal.h is enough.
>
> It's also weird. The option s
On Fri, Jun 8, 2012 at 1:15 AM, wrote:
> Do we need this for every file, or is one entry in qglobal.h enough?
>
One entry in qglobal.h is enough.
> As another solution, are there any compiler flags one can set to tell MSVC
> about the input encoding? If yes, we can simply add that to the qmake.
Yes, MinGW works well, the default input-char-set of which is UTF-8
,no matter whether BOM exists or not.
The behavior is the same as GCC under linux.
Debao
On Thu, Jun 7, 2012 at 12:52 PM, Konstantin Ritt wrote:
> #g++ -std=c++0x len.cpp
> #a.exe
>> It's quite good
>
> both gcc-4.4.0 and gcc-4.
Hi Thiago,
The real problem is caused by MSVC2005, as they can't generate UTF-8
exec-charset.
>From MSVC2010-SP1, they provided a workaround for this:
1) Source file saved with BOM
2) contains "#pragma execution_character_set("utf-8")"
This is not bad for Chinese users. Let's see what happened:
On Wed, Jun 6, 2012 at 12:05 AM, Thiago Macieira
wrote:
> The alpha package is too old. Can you retry with a recent Git version and let
> us know if the problem still happens?
>
The fail should be caused by the "space" in the path: "C:\Documents
and Settings\USER\My..."
__
You should go to qt-interest or qt-project.org/forums
This list is for developing Qt instead of developing with Qt.
Debao
2012/6/5 Daniel Kreuter :
> Hello,
>
> when I try to compile an Qt5 example I get the following error:
>
> jom: C:\Documents and Settings\USER\My
> Documents\Projekt\Qt5Multi
$ git push gerrit HEAD:refs/for/master
Counting objects: 15, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (8/8), done.
Writing objects: 100% (8/8), 854 bytes, done.
Total 8 (delta 7), reused 0 (delta 0)
fatal: Unpack error, check server logremote: Resolving deltas: 0%
I have no idea.
This patch works well under my computer: MSVC2010(32bit) Windows7
On Tue, Jun 5, 2012 at 12:43 AM, Stephen Kelly wrote:
>
> Hi there,
>
> For a bug fix I have a unit test which calls setTransientParent. The patch
> failed to integrate and I have a hunch that the setTransientParen
On Thu, May 24, 2012 at 12:47 PM, Thiago Macieira
wrote:
> For user applications (that is, other than qmake, moc, uic, etc.) that turned
> off QTextCodec, there's nothing that we can do. If you turn off the concept of
> codecs, then you can't change it.
>
Then
If we want to bootstrap tool such as
On Thu, May 24, 2012 at 12:47 PM, Thiago Macieira
wrote:
> You misunderstand Latin 1 then. If you read the contents with Latin1 and write
> using Latin1, you get exactly what you had before. No data is lost.
>
I know Latin1, I just forget that QString::toLocal8Bit() always equals
QString::toLatin
On Thu, May 24, 2012 at 10:26 AM, Thiago Macieira
wrote:
> On quinta-feira, 24 de maio de 2012 10.05.50, 1+1=2 wrote:
>> At present, when QT_NO_TEXTCODEC is defined, QTextStream use
>> QString::fromLatin1() /QString::toLocal8Bit()
>> to convert from/to bytes which looks lik
On Thu, May 24, 2012 at 2:51 AM, wrote:
> Not true. We do compile qutfcodec into qmake and the bootstrap tools, so
> QString::fromUtf8() does work. With the change of QString(const char *)
> to convert from utf8 I would assume that qmake at least partially uses
> utf8 by now.
>
> I think it make
Hi all,
It might be a bit late for 5.0.
But Qt 5 have started to enforce that source code file must be UTF-8.
So perhaps it make sense to change the default codec of QTextStream to
UTF-8.
This won't break many things, as the old behavior can be obtained by
calling QTextStream::setCodec().
I have
I have no idea,
And I hope that we can do some change for branch names:
master ==> qt4
qt5==> master
or simply merge qt5 ==> master
Regards,
Debao
On Tue, May 8, 2012 at 9:45 AM, Alberto Mardegan
wrote:
> Hi all,
> I've got a question about the QML Desktop components at:
> http
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.
>>
>
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 Tue, Apr 24, 2012 at 8:01 AM, wrote:
> There's no use in 'fixing' fromAscii(), toAscii() if we're deprecating it
> anyway (which I support). So just let it be a synonym to fromLatin1(),
> toLatin1(), which it was by default anyway in Qt4.
>
I like the idea.
_
Thiago Macieira has already answered your question. ;-)
On Sun, Apr 22, 2012 at 6:00 PM, Loaden wrote:
>> Seems you still use two different sets of source code.
> The current question is: Shall we need or no-need to use UTF-8 encoding as
> default?
> I thought we should use UTF-8 as default, Be
IMO, codecForXXX() is really a good news for China users. In the past
three years, I noticed that too many newcomers using these functions
in a wrong way.
such as
{{{
QTextCodec *codec = QTextCodec::codecForName("System");
QTextCodec::setCodecForLocale(codec);
QTextCodec::setCodecForCStrings(cod
Hi Loaden,
Seems you still use two different sets of source code.
* Under MSVC 2010, source files saved as UTF8 with BOM.
* Under Linux GCC, source files saved as UTF8 without BOM.
which means your application is not corss-platform.
And of course, this is a defect of C++ instead of Qt. You sh
Hi Loden,
The source code you provided if not cross-platform even under Qt4.
Under Windows platform, source file is save using encoding "GBK" while
under linux platform it saved as "UTF-8"
which means you are using two sets of source code for two platforms.
In addition, these are two errors(mis
4-bit targets. Nonetheless, mingw-w64
has retro-compatibility with the 32bit MinGW version, thus enabling a
2-in-1 build package for 32 and 64bit Windows systems.
On Thu, Apr 19, 2012 at 7:59 PM, wrote:
> On 19/04/2012 17:06, ext 1+1=2 wrote:
>>> From the homepage
Hi,
>From the homepage of project, http://mingwbuilds.sourceforge.net/
This is the MinGW-builds project ("mingwbuilds")
This project was registered on SourceForge.net on Mar 30, 2012, and
is described by the project team as follows:
Snapshots and releases builds of the MinGW compiler that u
Hi,
You can not compile it under Windows.
What you need is a modern linux which using wayland display server
protocol instead of the old X11 protocol.
Regards,
Debao
2012/4/2 Loaden :
> I don't know where to report bug about qtwayland.
> Any commens?
>
>>
>> main.cpp
>> .\main.cpp(41) : fatal
Hi,
I think we should remove it and make it done before api_changes merged
back to master.
Anyway, I have just pushed a commit for this
http://codereview.qt-project.org/21309
Debao
On Fri, Mar 23, 2012 at 7:13 AM, wrote:
> Hi,
>
> In the doc, it says:
>
> The default type when Qt 3 sup
Hi Stephen,
The pacth will fail to work
!isEmpty(MODULE):CONFIG += create_cmake
MODULE is not empty here, it is "winmain", as there is such a line
isEmpty(MODULE):MODULE = $$section($$list($$basename(_PRO_FILE_)), ., 0, 0)
at the begining of the qt_module_config.prf file.
Regards,
Deb
Hi,
The valid "help" options for configure under Windows are -help -h and -? .
After you perform "git clean -dfx" for qtbase, the "configure.exe"
will be removed.
When you run "configure -help" again, the "configure.bat" will
* generate "configure.exe" [Is this the issue you mentioned?]
* ru
Hi,
These files are not used for building Qt, they are needed for Qt user
who want to build they Qt Application with cmake instead of qmake.
Regards,
Debao
2012/3/21 Loaden :
> Hi, all! Just wonder, When build or install Qt, I can confirm there has some
> CMake files generated, e.g.
> D:\cmake\
Hi all,
http://codereview.qt-project.org/20730
QWorkspace had been called Q3Wrokspace before Qt4.0 finally released.
In a sense, it is a Qt3 support Widget.
And QWorkspace has been deprecated and replaced by QMdiArea at Qt4.3.
Should we remove it from Qt5?
And Friedemann Kleint has said that:
Hi,
Before this get fixed, we can simply set environment variable
"QT_QPA_PLATFORM" to the value "window:fontengine=native" under
windows, then all applications will work as expected.
IMO, it is not as bad as it seems, by doing this, users will become
more familiar with how to specify qpa plugin
changed to "qtbase\src\plugins\platforms\xlib", and run
qmake
make
the plugin will be generated.
Then, you can set Environment variable "QT_QPA_PLATFORM" to "xlib"
or simply pass command line options "-platform xlib" to your application.
Regards,
Debao
On Fri, Mar 16, 2012 at 5:04 PM, Bradley
Hi,
How about the xlib plugin?
Regards,
Debao
On Fri, Mar 16, 2012 at 3:45 PM, Bradley Smith wrote:
> OpenSUSE 11.1 appears to use libxcb-1.1. This version of XCB is too
> old for Qt 5 and gives compile errors.
>
> What is the minimum version of XCB required for Qt 5? What is the
> recommended
On Mon, Mar 12, 2012 at 12:22 PM, Davet Jacques wrote:
> Hi,
>
>
> I went over it and fixed most of
> the text to make it grammatically correct and nicer to read, but I don't
> understand what the following paragraph is supposed to mean (in the
> "SerialPort" section):
>
>> For the standard imple
Hi,
please use
return a.exec();
instead of
return 0;
Debao
2012/2/27 lata agrawal :
> Hi,
>
> I am running console application C1 in QProcess. I am starting this console
> application C1 from another console application C2. Problem is:
>
> I am only getting finished signal from C1 when I use
41 matches
Mail list logo
