On 21 Sep 2012, at 15:30, P Bai ap...@yahoo.com
wrote:
Thank you, Eike. From what I read in the codereview, a function to get the
scale factor qt_mac_get_scalefactor() is available as a patch, but
QPixmap/QImage HiDPI support is still a WIP. Does that mean even if I were
able to detect
this if the image as a correctly set DPI scale factor.
Patch is still not ready, sorry!
Morten
From: P Bai [ap...@yahoo.com]
Sent: Monday, September 24, 2012 8:59 PM
To: Sorvig Morten; development@qt-project.org
Subject: Re: [Development] Retina display support
P.S. using Windows Task manager to confirm some memory leaks is seems
quite stupid to me ;)
Why that's my favorite tool for detecting memory leaks of windows.. if the
numbers keep growing you have a problem.
Morten
___
Development mailing list
Help by offering your opinion on:
* Does the example have a meaningful purpose? Or is the feature it
demonstrates deprecated or obsolete in Qt 5?
* Does it follow Qt 5 best practice / recommended way of doing things?
* Are the comments, text strings, README, etc up to date?
* Is the example
Hi,
By now the pros and cons of the two approaches (free scaling vs. 2x) have
been well argued by Rutledge and Ziller; I'll go on an present the patches.
These implement the 2x type of high-dpi support.
In short, there is now an distinction between points and pixels. Window, widget
and event
-- could you please bottom post, that really improves thread readability :) --
Many of the new @digia folks are currently stuck with the Outlook web app wich
top-posts by default and does not support quoting. We'll figure it out
eventually.
Morten
While preparing an upcoming blog entry I've collected some best practices
regarding raster graphics (QImage and QPixmap). These apply to internal Qt
development as well. The patch is still pending so they are open for discussion.
(I use image and pixmap interchangeably here, most points apply
On Oct 9, 2012, at 10:59 AM, Pritam pritam_ghang...@infosys.com
wrote:
Forgive my ignorance, but I didn't understand. AFAIK most of Qt API is
in pixels. Do you mean after this patch, one should treat all API as points?
No problem, the concepts are new and I'm still figuring out how they apply
On Oct 9, 2012, at 11:32 AM, Olivier Goffart oliv...@woboq.com
wrote:
But QSize is already the size in pixel.
Or do you mean that QIcon::pixmap could return a pixmap that is larger than
the given QSize, scaled with some magic heuristics. That is not really
intuitive. (and violate the
Thiago:
On terça-feira, 9 de outubro de 2012 09.46.37, Sorvig Morten wrote:
I'm re-defining it to be the size in points. I think this intuitive, you are
asking QIcon::pixmap() for pixmap suitable for covering this many units on
screen - not for a pixmap of a specific size.
When you write
On Oct 9, 2012, at 1:53 PM, Olivier Goffart oliv...@woboq.com
wrote:
This is a behaviour change that breaks existing code (in applications and
in Qt), so it's opt-in via QT_HIDPI_AWARE.
I don't think having opt in like that is a good idea. It will be a mess when
you mix different
On Oct 9, 2012, at 1:55 PM, Christoph Feck christ...@maxiom.de wrote:
On Tuesday 09 October 2012 10:37:50 Sorvig Morten wrote:
While preparing an upcoming blog entry I've collected some best
practices regarding raster graphics (QImage and QPixmap). These
apply to internal Qt development
On Oct 11, 2012, at 9:36 AM, Samuel Rødal samuel.ro...@digia.com
wrote:
On 10/11/2012 08:23 AM, Ziller Eike wrote:
On 10.10.2012, at 16:56, Olivier Goffart wrote:
If you'd now be able to change the unit in Qt to pixel metrics for
certain widgets (and optionally sub widgets) where you
On Oct 10, 2012, at 7:46 PM, Thiago Macieira thiago.macie...@intel.com wrote:
nterpreted as good reasons to have a 4.9 release
Exceptions given on a case-by-case basis.
The above is much more than adding a symbol as an artifact of a change. It's
whole new API and features. It should not
On Oct 11, 2012, at 1:57 PM, Samuel Rødal samuel.ro...@digia.com
wrote:
It's unfortunate to potentially cause some extra trouble for a subset of
existing applications that wish to port to Qt 5, but weighed against the
utter embarrassment of the current fill rules I think we need this
On Oct 11, 2012, at 10:58 AM, Bache-Wiig Jens jens.bache-w...@digia.com wrote:
I have personally never seen an actual use case where a cosmetic pen makes
sense, but I assume there are reasons for having i so anyone creating an
explicit QPen(Qt::black, 0.0) should get a 1.0 pixel thick
On Oct 11, 2012, at 4:06 PM, BRM bm_witn...@yahoo.com wrote:
How about opt-in (via configure or extra flags) until the next major release?
I don't think doing the opt-in/opt-out/mandatory over several minor release
would bode well for compatibility between minor releases, which is a big
This is starting to sound like a candidate for a revert. However, we are still
unable to reproduce it here.
Are you able to debug it a bit more? Where do the mouse clicks go? Profile it
with instruments and see where it spins.
Morten
On Oct 16, 2012, at 7:18 PM, Stephen Chu step...@ju-ju.com
According to git grep Qt 4 has 47 semi-public exported qt_platform functions
offering platform-spesific functionality. Most platform code is now in plugins
and can no longer export symbols. We need a plan for dealing with these in Qt 5.
After a brief investigation these fall into several
On Oct 16, 2012, at 10:06 PM, Uwe Rathmann uwe.rathm...@tigertal.de wrote:
We are using QWS ( we don't even have X11 for the Carmine chip ) so this
is no problem - but by QWindow you mean Qt5 ?
Yes. I can't help you with QWS, sorry.
Morten
___
On Oct 19, 2012, at 9:31 AM, Knoll Lars lars.kn...@digia.com wrote:
Hi,
looks like there's quite some discussion about Thiago's proposal. Let's see
if we can get at least agreement on most of the changes and then focus on the
parts that are controversial.
To me this looks like a case
Dear Qt developers,
I got a new toy at work -- a 27 LCD with some crazy resolution
(2560x1440 IIRC), i,e. its pixel density is roughly 109 PPI. The LCD I
use at home has got a 94 PPI grid. I frequently move my laptop between
these two places and I have yet to make my KDE 4.9 use fonts which
On Oct 27, 2012, at 5:09 PM, Olivier Goffart oliv...@woboq.com wrote:
On Saturday 27 October 2012 14:16:18 Philip Ashmore wrote:
Hi there.
I'm talking about http://en.wikipedia.org/wiki/Google_Native_Client
Is anyone thinking of building Qt5 as nacl/pepper plugin?
The idea is to allow
On Oct 31, 2012, at 2:36 PM, Jarkko Laitinen jlaiti...@gmail.com wrote:
Hi,
I have been developing a cloud integration module for Qt. The working name
for the project is QCloud. It provides an API to do requests to Amazons S3
and Windows Azure. This has been my masters thesis project and
On Nov 2, 2012, at 8:42 AM, Kacper Gazda kga...@milosolutions.com wrote:
It's good news that Digia is targetting iOS and Android platforms, which have
huge user base, I wonder how are these ports going, though ?
You guys planning to have an alpha this year for any of the platforms ?
I am
On Nov 11, 2012, at 6:07 AM, Sze Howe Koh szehowe@gmail.com wrote:
Thanks for the explanation. I've opened tickets for this:
https://bugreports.qt-project.org/browse/QTBUG-27940
https://bugreports.qt-project.org/browse/QTBUG-27941
I asked because I'm working on patches for Qt
On Nov 13, 2012, at 2:17 PM, Koehne Kai kai.koe...@digia.com wrote:
Tukka and Qi Liang wants to see OS X 10.8 (maybe replacing 10.6) in the list.
The feasibility of this is probably something again for the CI system
maintainers + mac platform maintainer (Morten) to answer...
We should make
On Nov 14, 2012, at 4:24 PM, Christian Kandeler christian.kande...@digia.com
wrote:
On 11/14/2012 12:17 PM, Sorvig Morten wrote:
QtConcurrent is done. The implementation is not good enough to be used as a
base for further development.
Can you be a bit more specific? What are the general
On Nov 19, 2012, at 4:42 PM, Thiago Macieira thiago.macie...@intel.com wrote:
On segunda-feira, 19 de novembro de 2012 14.03.17, Konstantin Tokarev wrote:
- The core of a concurrency engine should be a work-stealing data
structure/scheduler. Qt Concurrent has simple work-stealing
On Nov 22, 2012, at 6:52 AM, Thiago Macieira thiago.macie...@intel.com
wrote:
That's the point: the conclusion was that the default on Mac is to *not* have
frameworks anymore. It might have been the case in the past, but recently the
trend has been to have regular libraries. Apple
On Nov 22, 2012, at 1:08 PM, Konstantin Tokarev annu...@yandex.ru
wrote:
22.11.2012, 16:04, Rutledge Shawn shawn.rutle...@digia.com:
On 22 Nov 2012, at 12:06 PM, Volker Götz wrote:
Yeah I know, and that's very convenient, but I've seen installers sometimes
too.
We could even offer a
Here are the changes:
https://codereview.qt-project.org/#change,40096
https://codereview.qt-project.org/#change,40215
And screenshots:
http://imgur.com/a/Zs6JJ
(You probably want to select the view in full resolution option for those)
This is a subset of the larger high-dpi patch presented
On Nov 29, 2012, at 10:47 AM, Jarkko Laitinen jlaiti...@gmail.com wrote:
Hi,
I sent a message to this mailing list a while ago and got couple of
responses. I have developed QCloud, an API that enables integration of Amazon
S3 and Windows Azure to Qt applications. The project has been
On Dec 11, 2012, at 1:30 PM, Alberto Mardegan ma...@users.sourceforge.net
wrote:
OK. Though I'd prefer to call it Qt::ForeignWindow, to make it obvious
that it's not owned by this process (Qt::NativeWindow just seems to tell
that the QWindow is associated with a native window, which is
On Dec 11, 2012, at 4:25 AM, Alan Alpert 4163654...@gmail.com wrote:
import Qt 5.0
Which imports all QML modules in the Qt Essentials released with 5.0.0
(except QtQuick 1). It would be the equivalent of
import QtQml 2.0
import QtQuick 2.0
import QtQuick.Window 2.0
import
Hi,
Currently my high-dpi work for Qt 4 lives in a separate repository on
github[0]. I would like to move it to gerrit/gitorious to make parallel
development with Qt 5 easier and be able to accept external contributions.
Can we create 4.8-highdpi?
Morten
[0]:
On Jan 16, 2013, at 9:22 AM, Bache-Wiig Jens jens.bache-w...@digia.com wrote:
Second, it would be useful to know if I am on a phone, tablet or
desktop platform. ( can already guess by the resolution but perhaps it
would be convenient to abstract it a bit.
These days you can't really
On Dec 24, 2012, at 8:22 AM, Alan Alpert 4163654...@gmail.com wrote:
For those interested in the matter, the discussion has now moved to
codereview.
https://codereview.qt-project.org/#change,43539 adds the QQmlApplicationEngine
https://codereview.qt-project.org/#change,43540 adds the qml
On Jan 16, 2013, at 5:16 PM, Attila Csipa q...@csipa.in.rs wrote:
On 16/01/13 17:36, Mohamed Fawzi wrote:
I am certainly not against the idea of a faster/more efficient static way of
choosing resources but it cannot depend on a predetermined directory
ordering. I believe we should rather
On Jan 29, 2013, at 1:05 PM, Oswald Buddenhagen oswald.buddenha...@digia.com
wrote:
moin *,
5.0 is out and the 5.1 feature freeze isn't that far off any more.
seems like the best time for some serious house cleaning.
therefore i'd like to urge everyone to give their pending changes which
On Jan 29, 2013, at 2:32 PM, Oswald Buddenhagen oswald.buddenha...@digia.com
wrote:
On Tue, Jan 29, 2013 at 12:41:13PM +, Sorvig Morten wrote:
On Jan 29, 2013, at 1:05 PM, Oswald Buddenhagen
oswald.buddenha...@digia.com wrote:
please explicitly mark the ones you still want to work
On Feb 7, 2013, at 1:42 PM, Sergei Nevdakh sergei.nevd...@gmail.com wrote:
Hi!
I haven't found any defininions of old platform defines Q_WS_MAC, Q_WS_WIN
in Qt5 sources, but these defines are still used in Qt itself.
Is it ok?
You are correct that those are not in use. They will be
Hi,
Getting ready for the 5.1 feature freeze, I think we should take some time
unifying the structure and API of the platform extras modules.
There has already been some private discussion on this topic, and this is an
attempt at reaching a final consensus. I think it's important that these
On Feb 28, 2013, at 4:50 PM, Thiago Macieira thiago.macie...@intel.com
wrote:
On quinta-feira, 28 de fevereiro de 2013 14.42.53, Tor Arne Vestbø wrote:
I'm probably missing something obvious here, but why are these not with
the class that they convert from?
- conversion operator (or
On Mar 1, 2013, at 12:28 AM, Thiago Macieira thiago.macie...@intel.com wrote:
On quinta-feira, 28 de fevereiro de 2013 21.32.26, Sorvig Morten wrote:
On Feb 28, 2013, at 4:50 PM, Thiago Macieira thiago.macie...@intel.com
wrote:
On quinta-feira, 28 de fevereiro de 2013 14.42.53, Tor Arne
On Mar 1, 2013, at 8:27 AM, Jake Thomas Petroules
jake.petrou...@petroules.com wrote:
Why are we discussing adding conversion operators from/to native objects in
QtCore/QtGui? The methods that did so were removed in Qt 5 in order to
increase modularity, why would we go the opposite
On Mar 1, 2013, at 10:37 AM, Jake Thomas Petroules
jake.petrou...@petroules.com
wrote:
I suppose it would not be a detriment. Where do you draw the line? Which
platforms, what functions and types?
I would leave that decision to the platform maintainers. An initial minimal set
would be
On Mar 4, 2013, at 8:13 AM, Samuel Rødal samuel.ro...@digia.com wrote:
What about things such as offscreen platform plugins used for testing?
Or what about a theoretical platform plugin that would stream rendering
commands to somewhere else? Imagine running wayland clients on Mac or
On Mar 4, 2013, at 11:56 PM, Thiago Macieira thiago.macie...@intel.com wrote:
Oh, and if you want simple, one more thing occurred to me:
runFunction([]() { main(); then(); });
If you need the return value:
runFunction([]() { then(main()); });
I will not accept C++11 isn't available
On Mar 5, 2013, at 8:38 AM, André Somers an...@familiesomers.nl
wrote:
I'd appreciate a reply on the point that when using a QFutureWatcher,
you don't know if the future is already done or not at the moment you
connect.
The intended usage of QFutureWatcher is that you set it up with
On Mar 11, 2013, at 5:12 AM, Jake Thomas Petroules
jake.petrou...@petroules.com wrote:
Are QMacCocoaViewContainer and QMacNativeWidget going to be implemented in
some Qt 5.x? I understand we currently have some implementation in
QtMacExtras, however the header files are still there in Qt 5
On Mar 11, 2013, at 2:44 PM, Frank Osterfeld frank.osterf...@kdab.com wrote:
Hi,
I see two ways to fix it, one is a one-liner, one's more work:
* Don't silently accept touch events if no item is waiting for them.
Ignoring the events triggers the touch-mouse fallback. That's the approach
On Mar 12, 2013, at 3:31 PM, Frank Osterfeld frank.osterf...@kdab.com wrote:
I tested with simple Hello-World style examples containing mouse areas
reacting to onClicked. Do you have anything else I should test specifically?
The demo is at https://github.com/msorvig/quick1cinematic .
What
On Mar 13, 2013, at 10:07 PM, Jake Thomas Petroules
jake.petrou...@petroules.com wrote:
So, the only thing left to say is that I hope the issue is not whether
QiOSStyle is welcome in QtGui at all, but simply whether it can be
technically achieved and whether there is someone to do the
On Mar 18, 2013, at 5:05 PM, Knoll Lars lars.kn...@digia.com wrote:
On 3/18/13 4:58 PM, Laszlo Papp lp...@kde.org wrote:
On Mon, Mar 18, 2013 at 3:52 PM, Thomas McGuire thomas.mcgu...@kdab.com
wrote:
QtSensors needs to be added to qt5.git, but couldn't yet, due to CI
failures.
See
On Mar 18, 2013, at 4:18 PM, Knoll Lars lars.kn...@digia.com wrote:
On 3/18/13 3:22 PM, Oswald Buddenhagen oswald.buddenha...@digia.com
wrote:
i'd like to raise a formal objection.
CI was virtually unusable for two weeks now.
due to that there is a completely unreasonable backlog of
There are cases where the platform plugin needs to block and check if Qt
accepts an event or not:
- ShortcutOverride: tryHandleShortcutEvent is synchronous (uses
QGuiApplicationPrivate:: shortcutMap directly) and returns a bool.
- CloseEvent: The platform needs to know if Qt cancels the
On Mar 21, 2013, at 10:55 PM, Thiago Macieira thiago.macie...@intel.com wrote:
Someone who knows about this, could you please take a look?
The first and third warnings are scary.
Fixed most of them:
https://codereview.qt-project.org/51868
https://codereview.qt-project.org/51869
On Mar 22, 2013, at 3:21 PM, Jake Thomas Petroules
jake.petrou...@petroules.com wrote:
Not the only way...
There's [NSApplicationDelegate applicationDockMenu:], and dock tile plugins
(we should look into bundling a default dock tile plugin in Qt apps!).
Fixed now (again):
On Mar 23, 2013, at 1:51 AM, Jake Thomas Petroules
jake.petrou...@petroules.com wrote:
I'd like to suggest that we add a new Q_OS_ define.
Currently, for Apple platforms, we have:
Q_OS_DARWIN
Q_OS_DARWIN32
Q_OS_DARWIN64
Q_OS_IOS
Q_OS_MAC
Q_OS_MAC32
Q_OS_MAC64
Q_OS_MACX
The first
On Apr 2, 2013, at 9:51 PM, Josh Faust jfa...@suitabletech.com wrote:
Actually, this seems to go beyond just using a custom SDK path. If I place
the 10.6 SDK alongside the others inside the Xcode application folder and
configure with:
./configure -developer-build -release -opensource
On Aug 23, 2013, at 10:32 AM, Olivier Goffart oliv...@woboq.com
wrote:
https://codereview.qt-project.org/#change,62948
is linked to a bug without categorization
This one went to stable because
- crash/infinite loop fix
- trivial patch for a corner case
- fix for new functionality.
I don't
These kinds of errors can usually be diagnosed by increasing the output
verbosity a bit. Try running macdeployqt myapp.app -verbose=2. Where does the
reference to QtScript come from?
Morten
On Aug 25, 2013, at 10:45 AM, qtnext qtn...@gmail.com wrote:
is there any chance that maceployqt will
I agree the Extra looks superfluous. In fact I'd like to go a bit further and
suggest we don't have platform extras at all and instead integrate the
functionality into Qt:
- Conversion functions for types in QtCore to QtCore
- Conversion functions for types in QtGui to QtGui
- Widgets to
wrote:
Most of the functionality was already in Qt 4 and was moved out for Qt 5
because of maintenance issues and different code for different platforms
exposed to the customer.
On 02/09/2013 10:35 PM, Sorvig Morten wrote:
I agree the Extra looks superfluous. In fact I'd like to go a bit
,64803.
--
J-P Nurmi
On Sep 4, 2013, at 2:35 PM, Tor Arne Vestbø tor.arne.ves...@digia.com wrote:
Yes yes a thousand times yes!
On 9/3/13 14:41 , Sorvig Morten wrote:
I think the advantages of having these functions available in QtCore/Gui
outweighs the risk of customers accidentally
On Oct 3, 2013, at 3:10 AM, Glen Mabey gma...@swri.org
wrote:
I'm on the dev branch but experienced this issue before the 5.2 and 5.3
branches split.
macbookpro:qtbase$ ./configure -prefix ~/src/take2/install
snip
Running configuration tests...
The test for linking against libxcb
On Oct 3, 2013, at 2:30 PM, Jørgen Lind jorgen.l...@gmail.com wrote:
But if you happen to have pkg-config in your path, why should we then
not use it. The user has one way or the other added it to the path,
so why shouldn't it be used.
I think the interesting question is why configure
I’d like to second (third?) going for approach 1.
It’s possible that we would want to implement secure socket support for
QWebSocket using native API instead of QTcpSocket
and OpenSSL at some point. We are currently doing this for
QNetworkAccessManager on OS X and iOS
On 02 Nov 2013, at 17:58, Thiago Macieira thiago.macie...@intel.com wrote:
On quarta-feira, 30 de outubro de 2013 07:29:56, Turunen Tuukka wrote:
We should have the applications made with Qt 4.8.5 on Mac OS 10.7 (for
example) working in 10.9 without serious issues. And we should be able to
On 05 Nov 2013, at 17:01, Matt Broadstone mbroa...@gmail.com wrote:
Cool,
I've been in touch with the macports patch author and he submitted a number
of his patches this morning for review. I'm sure they overlap, but perhaps
there are changes there that could help as well (I haven't
On 04 Nov 2013, at 10:49, John Layt jl...@kde.org wrote:
On 4 November 2013 08:22, Sletta Gunnar gunnar.sle...@digia.com wrote:
The work that was done is here:
https://codereview.qt-project.org/#dashboard,1002033
The work was abandoned after the transition to Digia and the author is no
On 15 Oct 2013, at 13:54, Eduardo Montesinos emontesi...@e-gits.com wrote:
Hi everybody,
Then I run qmake and open the generated xcodeproj in XCode, build and run in
simulator. The app starts up, but clicking on the TextInput field does no
effect, no keyboard on screen shows up. The lines
On 06 Nov 2013, at 17:18, Kai-Uwe Behrmann k...@gmx.de wrote:
What is the point of special casing sRGB?
sRGB is special for a couple of reasons:
- Most/Many of the images published for web are in the sRGB color space.
- OpenGL has support for sRGB textures and frame buffers.
Given that
On 05 Nov 2013, at 19:17, Shaw Andy andy.s...@digia.com wrote:
IIRC it wasn’t even compiled into the QtWidgets library, although the
documentation and everything existed, those symbols were never in Qt. Morten
can say 100% at least but that is my understanding and recollection at least.
On 14 Nov 2013, at 09:39, Stephen Kelly stephen.ke...@kdab.com wrote:
Hello,
I get build errors when trying to build qtbase dev branch for raspbian.
/home/stephen/dev/src/qtbase/src/tools/qdoc/qmlvisitor.cpp:51:0:
/home/stephen/dev/src/qtbase/src/tools/qdoc/qmlvisitor.h:78:29: error:
On 15 Nov 2013, at 09:37, Martin Smith martin.sm...@digia.com wrote:
On Nov 15, 2013, at 9:32 AM, Sorvig Morten morten.sor...@digia.com
wrote:
(and someone needs to port tools/qdoc/qmlparser)
I just did that a couple weeks ago. Has there been a more recent update?
No, it’s ok. I
On 27 Nov 2013, at 12:06, Adam Strzelecki o...@java.pl wrote:
I am hereby submitting my candidature. I am registered MaciOS developer. I
am personally interested to improve Qt experience on Mac, since I am using it
for several projects. I may either submit patches or fork Git master.
Of
On 27 Nov 2013, at 16:24, Ziller Eike eike.zil...@digia.com wrote:
Adding plugins into the respective frameworks would simplify deployment
significantly. macdeployqt's task would be reduced to inspecting the
frameworks the app links against, and copying the framework folders into
the
On 04 Dec 2013, at 11:47, Sletta Gunnar gunnar.sle...@digia.com wrote:
QWidget has the exact opposite problem. Layouts, styles and rendering happens
in pixel units while fonts are sized in point size. This is also a problem
when moving between platfoms as the pixelsize of a point has a
+1 from me as well.
Morten
On 17 Dec 2013, at 12:42, Knoll Lars lars.kn...@digia.com wrote:
Hi,
I’d like to nominate Paul Tvete as the formal maintainer of the QPA
architecture. He’s the original architect behind it anyway, and I don’t
think there are many people out there who know it
On 18 Dec 2013, at 01:22, Thiago Macieira thiago.macie...@intel.com wrote:
If it turns out that the failure to destroy is harmless, I'm not sure we
should do anything. If it's harmless, that means the extra work required to
free the memory is wasted, since it has no benefit to anyone. Just
On 21 Jan 2014, at 09:32, Simon Hausmann simon.hausm...@digia.com wrote:
On Monday 20. January 2014 20.21.14 deDietrich Gabriel wrote:
On Jan 20, 2014, at 7:55 PM, Allan Sandfeld Jensen k...@carewolf.com wrote:
On Monday 20 January 2014, Thiago Macieira wrote:
On segunda-feira, 20 de janeiro
On 21 Jan 2014, at 11:51, Simon Hausmann simon.hausm...@digia.com wrote:
On Tuesday 21. January 2014 10.23.22 Sorvig Morten wrote:
On 21 Jan 2014, at 09:32, Simon Hausmann simon.hausm...@digia.com wrote:
On Monday 20. January 2014 20.21.14 deDietrich Gabriel wrote:
On Jan 20, 2014, at 7:55
On 20 Jan 2014, at 21:21, deDietrich Gabriel gabriel.dedietr...@digia.com
wrote:
The truth is, market share doesn’t mean anything. Point in case: According to
the link above, OS X is less than 8% of the total market share. Should we
then drop the Mac port completely?
Good question! Possible
On 21 Jan 2014, at 13:20, Tor Arne Vestbø tor.arne.ves...@digia.com wrote:
On 21/01/14 11:23 , Sorvig Morten wrote:
I agree with many of these arguments, and I was in favor of setting
the minimum supported version to 10.7 back when we started Qt 5
development. But we did make
On 30 Jan 2014, at 01:15, John Layt jl...@kde.org wrote:
I've just pushed a 33 commit change set for this to Gerrit, my apologies to
the people I've tagged as reviewers :-) Any one else interested, feel free
to
jump in and help.
There's 4 main new classes:
* QPageSize
* QPageMargins
Will this patch work?
https://codereview.qt-project.org/#change,80620
Morten
On 11 Mar 2014, at 12:12, Kurt Pattyn pattyn.k...@gmail.com wrote:
Some more information.
I work on OSX.
When digging into the platform specific implementation, I detected that in
the method
On 22 Apr 2014, at 12:49, Simon Hausmann simon.hausm...@digia.com wrote:
On Monday 21. April 2014 15.13.08 Robert Knight wrote:
The design direction is because QML is easier to develop with, more
modern,
and based on OpenGL. Widgets don't have that and will never be as
efficient.
+1 from me as well.
In addition to his submissions Jake is knowledgeable about all things Mac and
has provided solid advice on several occasions.
Morten
On 16 Apr 2014, at 09:08, Christian Kandeler christian.kande...@digia.com
wrote:
On 04/15/2014 07:13 PM, Thiago Macieira wrote:
I'd like
On 29 Apr 2014, at 00:39, Thiago Macieira thiago.macie...@intel.com wrote:
Em ter 29 abr 2014, às 00:16:43, Jeremy Lainé escreveu:
On 04/28/2014 11:44 AM, Nichols Andy wrote:
It is possible still in the packaged versions of Qt for iOS to make
connections using SSL via QNetworkAccessManager
On 29 Apr 2014, at 13:31, Richard Moore r...@kde.org wrote:
I actually started thinking about how a smaller API for some of this could
look. Basically with the idea being that for many applications only a subset
of the full QSslXX apis mattered. If you want me to post my notes (such as
On 11 May 2014, at 21:53, Tim Blechmann t...@klingt.org wrote:
the 32bit versions seem to use the _debug suffix ... the difference does
not occur in all frameworks, but only in:
QtCore.framework
QtMultimediaQuick_p.framework
QtPrintSupport.framework
QtScriptTools.framework
Over the past year-and-a-half we’ve implemented high-dpi scaling for Qt on Mac
OS X and iOS. Now we have an excellent opportunity to bring this support to
other platforms.
A quick recap for those unfamiliar: This high-dpi mode is an alternative to the
traditional DPI scaling. In the
On 23 May 2014, at 18:30, Thiago Macieira thiago.macie...@intel.com wrote:
Em sex 23 maio 2014, às 07:20:42, Sorvig Morten escreveu:
Adding support to QtWayland looks like a win to me. Do we want to add
platform-indepent support to Qt?
I think my question is: why wouldn't we?
The platform
On 26 May 2014, at 07:59, Ziller Eike eike.zil...@digia.com wrote:
On May 23, 2014, at 6:03 PM, m...@rpzdesign.com wrote:
Sorvig:
From the latest new front:
http://bgr.com/2014/03/18/nexus-9-specs-details/
Digitimes on Tuesday cited its own research arm in reporting that Google
On 26 May 2014, at 22:40, Daiwei Li daiwe...@gmail.com wrote:
I took a stab at adding high DPI support to Android and created a review
here: https://codereview.qt-project.org/#change,86260. I would appreciate any
feedback (e.g. what tests need to be added, what other corner cases need to
On 27 May 2014, at 11:47, Daiwei Li daiwe...@gmail.com wrote:
Hi Morten,
My understanding of your platform independent change was that it would let
the scale factor be set by the user at runtime with an environment variable.
Is it meant to replace all platform plugin scaling (I.e. iOS and
On 27 May 2014, at 18:36, Daiwei Li daiwe...@gmail.com wrote:
BTW, any idea when your platform independent high DPI changes will
make it in (or be in a working state in the review)? I would love to
try having Android scale using the platform independent code.
The patches are now in a
On 05 Jun 2014, at 00:25, Thiago Macieira thiago.macie...@intel.com wrote:
Em qua 04 jun 2014, às 10:32:17, Olivier Goffart escreveu:
In general, i think it would be beneficial to have some public API in
QObject to create dynamic signals or slots.
This has been asked from the QML-on-Go
1 - 100 of 157 matches
Mail list logo
