On Mon, Sep 22, 2014 at 1:03 PM, Sorvig Morten morten.sor...@digia.com wrote:
On 19 Sep 2014, at 11:28, Sorvig Morten morten.sor...@digia.com wrote:
This will indeed receive attention in the coming days. There are already
some patches attached to the QTBUGs. I’ll post back here once we have
Hi,
Thanks for your feedback related to qt.io opensource downloads page:
http://www.qt.io/download-open-source/
The page is now updated based on your comments - the major changes are:
1. Automatic download is now completely removed
* Recommended download is still highlighted and you can start
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 with a base class for uninterpreted platform strings.
On Tue, Oct 7, 2014 at 9:13 AM, Anttila Janne
janne.antt...@theqtcompany.com wrote:
Hi,
Thanks for your feedback related to qt.io opensource downloads page:
http://www.qt.io/download-open-source/
The page is now updated based on your comments - the major changes are:
1. Automatic download
Hi Kuba,
Your criticisms are completely valid, and the conclusions you draw from them
are, too. The problems Thiago lists make this a daunting task, but mostly not
because of complexity, but of sheer volume of code that needs to be modified.
I believe it's worth it, but most of us here lack
Hi all,
There seems to be real issue with qt5.git integration in 'dev' branch.
Someone, please check and fix this.
Br,
Jani
-Original Message-
From: Qt Continuous Integration System (Code Review)
[mailto:gerrit-nore...@qt-project.org]
Sent: 7. lokakuuta 2014 11:08
To: Qt Submodule
On Oct 7, 2014, at 8:30 AM, Julien Blanc julien.bl...@nmc-company.com wrote:
On 07/10/2014 12:11, Tomasz Siekierda wrote:
For file paths, I feel QString is really enough.
Changing it to something else because of a few corner cases seems like
an overkill to me. We already have a lot of
El Tuesday 07 October 2014, Tomasz Siekierda escribió:
For file paths, I feel QString is really enough.
Changing it to something else because of a few corner cases seems like
an overkill to me.
Just for the sake of documenting the issue and pointing to this thread if
future questions arise:
On Tuesday 07 October 2014 10:38:47 Kuba Ober wrote:
Just to be very clear: it is currently impossible to make a truly portable
file management utility with Qt’s core APIs. Why? Because it will simply
ignore all file names that it can’t decode when iterating the directory,
and it won’t be able
Hi,
I cannot get my changes [1] through CI for qtdeclarative/5.4. Originally it
failed with qquickwindow tests, but now it does not compile on Windows CE
platform.
Can anyone take a look at the situation?
1. https://codereview.qt-project.org/96314
Best,
Oleg
On 07-Oct-14 18:21, Oleg Shparber wrote:
I cannot get my changes [1] through CI for qtdeclarative/5.4. Originally
it failed with qquickwindow tests, but now it does not compile on
Windows CE platform.
Can anyone take a look at the situation?
1. https://codereview.qt-project.org/96314
This
Hi everyone,
any chance to get a hold on a MinGW snapshot of the 5.4.0 beta ?
I personally hate to use Micro$oft stuff and I much prefer the good old shell :)
The snapshot would allow me to decide if I need to open a bug about buttons
background palette on Windows. The code works fine on Linux.
The problem is serious enough, indeed, that Python 3 has resorted to a hack
where they use a private Unicode range to encode the bytes between 128
and 255 in strings that fail normal decoding. I think that putting this hack
into
QString is unthinkable, and the concept of a platform string
On Tuesday 07 October 2014 23:19:23 Tony Van Eerd wrote:
The problem is serious enough, indeed, that Python 3 has resorted
to a hack where they use a private Unicode range to encode the
bytes between 128 and 255 in strings that fail normal decoding.
I think that putting this hack into
14 matches
Mail list logo
