On 10/04/2014 08:36 PM, Lisandro Damián Nicanor Pérez Meyer wrote:
Hi! A fellow maintainer in Debian has packaged qbs as a separate source. So we
though of building qtcreator's qbsprojectmanager and qbs plugin with it.
This seems not supported right now out of the box
Hm, what do you mean by
Cornelius Hald wrote:
AFAIK QtMultimedia on Linux uses Gstreamer for video and audio playback,
so installing the right Gstreamer plugins should (hopefully) fix this
issue.
Maybe this will help:
https://apps.ubuntu.com/cat/applications/gstreamer0.10-plugins-bad/
One big problem is that it's
Hi,
Thiago Macieira wrote:
Question to the folks who follow Windows CE development:
is there any light at the end of the tunnel about compiling C++11 code for
that platform?
Basically, Windows CE support right now completely blocks any idea of
using C++11 code in Qt, since the only
There always were gcc versions that could compile to Wince, but getting that
to work with the microsoft libs etc is quite a hassle, never bugfree and you
loose the ability to use visual studio for debugging, remote deployment, etc.
Or in short most customers won't even bother to look.
--
Gentlemen,
If images are placed to resource file,
is there any option for an automatic management
of using either Retina or non-Retina images
using Apple's naming convention or the manual
management is the only option like for Mac OS X?
Here's an example of what Qt developers
are doing:
On 26/09/14 00:31, Thiago Macieira wrote:
On Thursday 25 September 2014 16:33:12 Tomaz Canabrava wrote:
Long that that I have send this e-mail already, but better late than never.
In the Qt Develompent Summit I raised my hand to get one dirty thing done:
The Settings.
After a good while
On Monday 06 October 2014 10:51:28 Christian Kandeler wrote:
[snip]
Then I got to the point in where the qbsprojectmanager needs hostosinfo.h
which is not provided by qbs by default nor as a private header/lib.
That's a bug. Creator must not include this private header. I will
provide a
I’ve just read Armin Ronacher’s blog post about Unicode in Python 3, and he has
highlighted a possible problem with “Unicode everywhere” approach to things
that come from byte APIs like one has on Unix.
File names can have any encoding, and a file name not being valid under the
encoding given
On Monday 06 October 2014 11:12:57 Kuba Ober wrote:
Thus, how does Qt deal with a directory listing with such “invalid” file
names? Do they survive the round-trip through a QString and QDirIterator?
Would it be worthwhile to tackle this issue in a better fashion (whatever
it might be) for Qt
On Oct 6, 2014, at 11:21 AM, Thiago Macieira thiago.macie...@intel.com wrote:
On Monday 06 October 2014 11:12:57 Kuba Ober wrote:
Thus, how does Qt deal with a directory listing with such “invalid” file
names? Do they survive the round-trip through a QString and QDirIterator?
Would it be
On Monday 06 October 2014 13:30:29 Kuba Ober wrote:
This was discussed to exhaustion in Qt 5's development process. The
conclusion is to remain at status quo since there is no good, technical
solution.
I’d think that the solution could be to use a dedicated class for file
names, perhaps
On Oct 6, 2014, at 2:45 PM, Thiago Macieira thiago.macie...@intel.com wrote:
On Monday 06 October 2014 13:30:29 Kuba Ober wrote:
This was discussed to exhaustion in Qt 5's development process. The
conclusion is to remain at status quo since there is no good, technical
solution.
I’d think
2014-10-06 23:53 GMT+04:00 Kuba Ober k...@mareimbrium.org:
On Oct 6, 2014, at 2:45 PM, Thiago Macieira thiago.macie...@intel.com
wrote:
How do you pass it on the command-line? Mind you, QProcess takes a
QStringList
for arguments.
It look as if we’d need something like QPlatformString
13 matches
Mail list logo
