Re: [Development] QBackingStore and alien widgets

On 05/02/2013 11:11 PM, Rafael Roquetto wrote: > Hello, > > While debugging the QNX platform plugin, I found out that when > QWidget::winId() > is called on a non-toplevel widget, it will still use its parents > QBackingStore for rendering. Is this really the intended behavior? > > This behavior i

Re: [Development] kdelibs coding style

On 04/29/2013 10:31 PM, Olivier Goffart wrote: > On Monday 29 April 2013 09:43:55 Thiago Macieira wrote: >> On segunda-feira, 29 de abril de 2013 17.16.49, Sergio Martins wrote: >>> The thing is, I just discovered that the kdelibs style[1] has a little >>> difference from Qt, it uses braces for one

Re: [Development] Spring-cleaning the Gerrit dashboards, again

On 03/20/2013 07:31 PM, Thiago Macieira wrote: > Can we please agree on cleaning the dashboards up? Or, if we've agreed, can we > do it? > > My dashboard is unusable. For a few months now, I have stopped my daily look > at the "Review Requests" section. As a result, I have missed important reviews

Re: [Development] integer bug in Qt4.8.x

On 03/06/2013 11:38 AM, Thomas Senyk wrote: > Hi, > > I think I stumbled over a bug in Qt4.8.x - QtDeclarative, but I wanted to > asked for opinions first. > > First of all: This is not happening in Qt5 (neither QtQuick2.0 nor QtQuick > 1.1) > > This seems to only happen on ARM... at least I couldn

Re: [Development] Qt Platform Extras

On 03/04/2013 01:08 PM, Sorvig Morten wrote: > > On Mar 4, 2013, at 8:13 AM, Samuel Rødal 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 s

Re: [Development] Qt Platform Extras

On 03/01/2013 11:22 AM, Friedemann Kleint wrote: > Hi, > > >I suppose it would not be a detriment. Where do you draw the line? > Which platforms, what functions and types? Here are some candidate types > for constructors and conversion operators... > > The thing to keep in mind is basically that

Re: [Development] Pushing rebases and unrelated changes together is a sin

On 02/20/2013 01:01 PM, Shawn Rutledge wrote: > On 20 February 2013 09:43, Samuel Rødal wrote: >> On 02/20/2013 09:22 AM, Thiago Macieira wrote: >>> On quarta-feira, 20 de fevereiro de 2013 08.47.40, Samuel Rødal wrote: >>>> The correct process when doing rebases i

Re: [Development] Pushing rebases and unrelated changes together is a sin

On 02/20/2013 09:22 AM, Thiago Macieira wrote: > On quarta-feira, 20 de fevereiro de 2013 08.47.40, Samuel Rødal wrote: >> The correct process when doing rebases is: >> >> git pull --rebase # or your favorite git work-flow >> git push gerrit HEAD:refs/for/some_branch &g

[Development] Pushing rebases and unrelated changes together is a sin

Hello, it happens quite regularly that people do a rebase and in addition do changes in the same push. It looks like this: git pull --rebase # or cherry-pick or whatever you do # do some changes git commit -a --amend git push gerrit HEAD:refs/for/some_branch and it makes the diff between patch

Re: [Development] Qt 5.1 feature set and freeze date

On 02/14/2013 12:11 PM, Poenitz Andre wrote: > Rodal Samuel wrote: >> On 02/14/2013 10:39 AM, Poenitz Andre wrote: >>> Samuel Rødal wrote: >>>> What use is a QPlatformPixmapHandle having per-platform typedefs >>>> (xcb_pixmap_t, HDC, etc) without #ifdefs

Re: [Development] Qt 5.1 feature set and freeze date

On 02/14/2013 10:39 AM, Poenitz Andre wrote: > Samuel Rødal wrote: >> What use is a QPlatformPixmapHandle having per-platform typedefs >> (xcb_pixmap_t, HDC, etc) without #ifdefs to manipulate it using native >> code in the first place? >> >> Can you give a plat

Re: [Development] Qt 5.1 feature set and freeze date

On 02/13/2013 08:58 PM, André Pönitz wrote: > On Wed, Feb 13, 2013 at 10:08:31AM +0100, Friedemann Kleint wrote: >> Hi, >> >> we also plan to start Qt Windows Extras to bring at least the missing >> image conversion functions ( QTBUG-27103 ) back provided we can find >> someone to create the repos

Re: [Development] B-Tree containers instead of STL in Qt

On 02/08/2013 09:51 AM, Illya Kovalevskyy wrote: > Hello. > > I found one Google thing, a useful thing - > http://google-opensource.blogspot.com/2013/01/c-containers-that-save-memory-and-time.html. > According to benchmarks: they are faster than STL containers. For some use cases. As they note if

Re: [Development] Nominating Andreas Hanssen as Approver

On 02/06/2013 10:42 PM, Olivier Goffart wrote: > On Wednesday 06 February 2013 13:31:40 Thiago Macieira wrote: >> Hello >> >> Andreas is a long-time Qt developer. For those of you who haven't yet had >> the pleasure of meeting him, he's the brains behind the original >> implementation and maintenan

Re: [Development] issue in minimal plugin

On 01/31/2013 01:53 PM, Paul Olav Tvete wrote: > On Wednesday 30 January 2013 07:58:25 Thiago Macieira wrote: >> On quarta-feira, 30 de janeiro de 2013 17.17.46, Mumtaz Ahmad wrote: >>> Hi, >>> >>> I am trying to run rasterwindow example using minimal plugin but i am >>> getting null paint device >

Re: [Development] QGraphicScene with thousands of QGraphicItems freezes the APP

On 01/24/2013 08:35 AM, Samuel Rødal wrote: > On 01/23/2013 08:02 PM, Jose wrote: >> Hello, >> >> I am developing a Qt-based application. The main part of the application >> if a QGraphicView widget >> whose scene is populated with thousands (sometimes hundreds

Re: [Development] QGraphicScene with thousands of QGraphicItems freezes the APP

On 01/23/2013 08:02 PM, Jose wrote: > Hello, > > I am developing a Qt-based application. The main part of the application > if a QGraphicView widget > whose scene is populated with thousands (sometimes hundreds of > thousands) of QGraphicItems, more > precisely a subclass because to overload the "p

Re: [Development] Nominating Uli Schlachter (psychon) for Approver

On 01/17/2013 08:17 AM, Thiago Macieira wrote: > On quinta-feira, 17 de janeiro de 2013 08.05.10, Samuel Rødal wrote: >>> I have never heard of Uli's name before and I cannot find any email from >>> him to this mailing list. Maybe all of the discussion on XCB was hel

Re: [Development] Nominating Uli Schlachter (psychon) for Approver

On 01/16/2013 05:47 PM, Thiago Macieira wrote: > On quarta-feira, 16 de janeiro de 2013 16.36.01, Robin Burchell wrote: >> Hi, >> >> I'd like to nominate Uli (psychon on IRC) for Approver status. >> >> Uli has some specialist knowledge that is often hard to find in any >> appreciable quality: he kn

Re: [Development] OpenGL in Qt 5.1 and onwards

On 01/16/2013 09:58 AM, Sean Harmer wrote: > On Wednesday 16 January 2013 08:12:37 Samuel Rødal wrote: >> On 01/15/2013 05:05 PM, Sean Harmer wrote: >>> On Tuesday 15 January 2013 16:37:38 Samuel Rødal wrote: >>>> On 01/15/2013 02:43 PM, Sean Harmer wrote: >

Re: [Development] Proposal: expose the OS/platform in QML

On 01/16/2013 08:21 AM, Bache-Wiig Jens wrote: > > On Jan 15, 2013, at 6:38 PM, Attila Csipa wrote: > >> On 15/01/13 18:27, Nurmi J-P wrote: >>> What do you think about exposing the underlying operating system and/or >>> platform name in QML? >>> ... >>> Which one of these proposals do you like t

Re: [Development] OpenGL in Qt 5.1 and onwards

On 01/15/2013 05:05 PM, Sean Harmer wrote: > On Tuesday 15 January 2013 16:37:38 Samuel Rødal wrote: >> On 01/15/2013 02:43 PM, Sean Harmer wrote: >>> Hi, >>> >>> On Monday 07 January 2013 10:00:47 Sean Harmer wrote: >>>> On Monday 07 January 20

Re: [Development] OpenGL in Qt 5.1 and onwards

On 01/15/2013 02:43 PM, Sean Harmer wrote: > Hi, > > On Monday 07 January 2013 10:00:47 Sean Harmer wrote: >> On Monday 07 January 2013 08:28:35 Sletta Gunnar wrote: >>> On Dec 18, 2012, at 2:34 PM, Sean Harmer wrote: Hi, I would like to start a discussion on the future level of sup

Re: [Development] submitting a multi-dimensional container class for Qt: QNDArray

On 01/11/2013 02:41 PM, Glen Mabey wrote: > > On Jan 11, 2013, at 2:03 AM, Samuel Rødal wrote: > >> On 12/28/2012 03:36 PM, Glen Mabey wrote: >>> Hello, >>> >>> For some time, I have been working on a QtCore-based class that would be a >>> conta

Re: [Development] submitting a multi-dimensional container class for Qt: QNDArray

On 12/28/2012 03:36 PM, Glen Mabey wrote: > Hello, > > For some time, I have been working on a QtCore-based class that would be a > container class of arbitrary dimensionality. I did give a presentation on > this topic at DevDays-CA: > > http://www.qtdeveloperdays.com/northamerica/sites/default/

Re: [Development] QT5.0 PlatformSupport info needed

On 01/11/2013 08:43 AM, Thiago Macieira wrote: > On sexta-feira, 11 de janeiro de 2013 08.20.16, Samuel Rødal wrote: >> On 01/10/2013 08:08 PM, Mumtaz Ahmad wrote: >>> Hi, >>> >>> I am trying to port QT5.0 . I made a headless reference >>&g

Re: [Development] QT5.0 PlatformSupport info needed

On 01/10/2013 08:08 PM, Mumtaz Ahmad wrote: > > > Hi, > > I am trying to port QT5.0 . I made a headless reference > implementation on linux using minimal plugin. On linking i had to > link libQt5PlatformSupport.a as well. On the first look it appears > that platformsupport is wr

Re: [Development] OpenGL in Qt 5.1 and onwards

On 12/18/2012 02:34 PM, Sean Harmer wrote: > Hi, > > I would like to start a discussion on the future level of support for OpenGL > enablers in Qt for those that are interested. So here goes... > > I would like to add in a bunch more OpenGL enablers but am not sure on where > to best put them. Some

Re: [Development] OpenGL in Qt 5.1 and onwards

On 01/07/2013 08:28 AM, Yves Bailly wrote: > Greetings all, > > Le 18/12/2012 14:34, Sean Harmer a écrit : >> I would like to start a discussion on the future level of support for OpenGL >> enablers in Qt for those that are interested. So here goes... > > This may be a bit off-topic, but I have a l

Re: [Development] Is QGLWidget broken on Qt4/QPA?

On 12/19/2012 05:34 PM, Rafael Roquetto wrote: > Hello, > > I think I might have stumbled upon a bug in QGLWidget affecting QPA platforms. > This happens at least in BlackBerry, but I suspect it is a general issue. > > When a QGLWidget is instantiated, a new native window is created once > Q[GL]Wid

Re: [Development] X Error: BadDrawable with Qt4.8.4

On 12/19/2012 02:31 AM, chenyw3892 wrote: > I compiled Qt4.8.4 in Redhat6(i386), but when I run my application, X > Error: BadDrawable(invalid Pixmap or Window parameter) 9 ocurrerd Try to run your application with "-graphicssystem native" or do QApplication::setGraphicsSystem("native"); before i

Re: [Development] [Qt-creator] gerrit-speak

> There's a point though that a lot of people (including me) are using -1 for > 'this requires more work', and -2 for 'the patch, or target branch is just > wrong, please abandon'. So if the intention of the patch is fine in general, > but contains some errors, I myself tend to give -1, though i

Re: [Development] Making sure all platform plugin library names are prefixed with "q"

On 12/11/2012 10:01 AM, Samuel Rødal wrote: > Hello, > > currently the platform plugin library name is a bit inconsistent. In > most cases it will have the "q" prefix, for instance libqeglfs.so, > libqminimal.so, libqcocoa.so, etc. > > However, the qnx, window

Re: [Development] Foreign windows, embedding and transiency

On 12/11/2012 01:30 PM, Alberto Mardegan wrote: > On 12/11/2012 12:47 PM, Sorvig Morten wrote: >> I've been planning this a bit from he perspective if the Cocoa port, here's >> what I think I need: >> >> - A Qt::WindowFlags flag ("Qt::NativeWindow") > > OK. Though I'd prefer to call it Qt::Foreign

Re: [Development] Foreign windows, embedding and transiency

On 12/11/2012 12:45 PM, Sletta Gunnar wrote: > > On Dec 11, 2012, at 12:33 PM, Samuel Rødal > wrote: > >> On 12/11/2012 12:03 PM, Alberto Mardegan wrote: >>> Hi all, >>> while digging a bit more deeply into the code of QX11EmbedWidget (in >>> ord

Re: [Development] Foreign windows, embedding and transiency

On 12/11/2012 12:03 PM, Alberto Mardegan wrote: > Hi all, > while digging a bit more deeply into the code of QX11EmbedWidget (in > order to port it to Qt5), I started wondering if we really need a > special API for embedding, or whether QWindow could already offer most > of it: > > == >

Re: [Development] Question on QWS/QPA

On 12/11/2012 09:53 AM, Arunprasad Rajkumar wrote: > Hi Samuel, > > Thanks for your reply. We would like to have only QtWebKit widget and > not going to use QtQuick at this moment. So by default QPA/QWS client > will render widgets on shared memory allocated via Qt and draws on it. > Once done it r

[Development] Making sure all platform plugin library names are prefixed with "q"

Hello, currently the platform plugin library name is a bit inconsistent. In most cases it will have the "q" prefix, for instance libqeglfs.so, libqminimal.so, libqcocoa.so, etc. However, the qnx, windows, and xcb libraries were named libqnx.so, libwindows.so, and libxcb.so respectively. The la

Re: [Development] QAction-like API for QML

On 12/11/2012 04:39 AM, Alan Alpert wrote: > The QMenu API allows for adding menu separators too, but I haven't > seen those in apps for a while. Is it worth adding another type or > flag to integrate separators into the Action API? Couldn't menu separators automatically be added between each non

Re: [Development] Running Qt auto-tests offscreen

On 12/07/2012 05:33 PM, Thiago Macieira wrote: > On sexta-feira, 7 de dezembro de 2012 17.12.06, Jedrzej Nowacki wrote: >>> I agree in theory, provided that the tests that do stress out the >>> integration are close to complete testing. In practice, there's no way to >>> tell whether the testing is

[Development] Running Qt auto-tests offscreen

Hello, do you use the CI system as a way to run the auto-tests? Are you tired of having to wait forever for the widgets auto-tests to run, at the same time as they pop up a hundred windows and dialogs that steal the focus and prevent you from doing any work? In that case I'm working on a solut

Re: [Development] Question on QWS/QPA

On 12/06/2012 08:00 PM, Arunprasad Rajkumar wrote: > Hello Developers, > > I'm new to QT. Basically I understood like QWS/QPA reduces porting QT to > custom embedded devices without touching the core functionality of > QtGui. Also it is a architectural split down of functionality and > porting laye

[Development] Heads up: Late API removal from QWindow

Hello, with the iOS platform port coming along we've done some discussions regarding the whole orientation story in Qt. There are two main ways of doing orientations in Qt at the moment, depending on the platform. On desktop platforms, orientation changes typically happen when you rotate your

Re: [Development] Comparing two reals in Qt code

On 11/29/2012 03:01 PM, Dominik Holland wrote: > Hi all, > > last month i had some performance problems on a QML animation running on > low end hardware (imx233). > I debugged that problem and it was caused because of rounding errors > during the comparison of two reals. What kind of QML code lead

Re: [Development] Heads up: Source incompatible change for qtbase

On 11/30/2012 02:15 PM, Robin Burchell wrote: > On Fri, Nov 30, 2012 at 2:10 PM, Sergio Ahumada > wrote: >> I wonder if these should be documented under dist/changes-5.0.0 ? > > Well, this specific example is removal of API added within 5.0.0, > isn't it? So I don't see why it makes sense to docum

[Development] Heads up: Source incompatible change for qtbase

Hello, I take the blame for breaking the qtwebkit build by merging the QQuickItem::pos() API change, and fully agree with Simon that a good way to prevent these issues in the future is to send a notice to the mailing list about SIC changes. We're now trying to get https://codereview.qt-project

Re: [Development] Comparing two reals in Qt code

On 11/30/2012 09:51 AM, Jedrzej Nowacki wrote: > On Friday 30. November 2012 09.23.32 Samuel Rødal wrote: >> Yep, having something similar to AlmostEqualUlpsAndAbs() would be great. >> I've had some ideas of making qFuzzyCompare work that way in the past, >> but gave the

Re: [Development] Comparing two reals in Qt code

On 11/29/2012 07:38 PM, Sean Harmer wrote: > On 29/11/2012 18:34, BRM wrote: >>> From: Alan Alpert <4163654...@gmail.com> >>> Sent: Thursday, November 29, 2012 11:52 AM >>> Subject: Re: [Development] Comparing two reals in Qt code >>> >>> On Thu, Nov 29, 2012 at 6:53 AM, Sean Harmer wrote:

Re: [Development] QML Tooling Renames (was: Pending decisions on co-installation)

On 11/20/2012 05:05 PM, Alan Alpert wrote: > On Tue, Nov 20, 2012 at 8:00 AM, Jana Aurindam > wrote: >> To summarize QML tool naming discussion so far: In qtquick1 repo qmlviewer -> qml1viewer qmlplugindump -> qml1plugindump >> >>> That's already the name, isn't it? >> >

Re: [Development] QX11EmbedWidget in Qt5

On 11/08/2012 10:37 AM, Alberto Mardegan wrote: > Hi all! >At some point I might need to use XEmbed, so I'm interested in helping > out the implementation of QX11EmbedWidget in Qt5, as time permits. > Now I'm just studying the code to evaluate how much of an effort it > would be. Excellent :)

Re: [Development] Qt 4.8.4 release candidates are available

On 10/23/2012 12:36 PM, Taipale Juhani wrote: > Hi all, > > Now there are Qt 4.8.4 release candidate packages available for public > review. > > These are not yet the official release packages and should not be used > as such. > > Packages are built against SHA1: 8869b3b30a29b1dd4218b3f5ac0bec9dd93

Re: [Development] qt-5 beta1 can't build with -no-opengl support

On 11/01/2012 11:13 AM, thouraya andolsi wrote: > Hi, > Trying to build QT-5 without the opengl support, I got an output like: > > ../../include/QtQuick/../../../../qtdeclarative/src/quick/scenegraph/coreapi/qsggeometry.h:117:25: > error: 'GLenum' has not been declared > > ../../include/QtQuick/../

Re: [Development] Qt5 Beta/Qt Quick 2.0 and Antialiasing

On 10/30/2012 11:14 AM, Labs, Torsten wrote: > Hello, > we created some prototype with Qt Quick 2 on a ARM board. Its running > verry well except antialiasing. As i can see in the Qt5 Documentation > # there is a new flag for antialiasing **antialiasing >

Re: [Development] New maintainers

On 09/20/2012 03:54 PM, Thiago Macieira wrote: > On quarta-feira, 19 de setembro de 2012 12.08.14, Knoll Lars wrote: >> Hi, >> >> I'd like to nominate a couple of new maintainers for some parts of Qt >> currently lacking a maintainer. > > Oops, I missed the "I'd like to nominate" part. > >> For the

Re: [Development] xcb-icccm dependency in Qt 5/libxcb

On 10/25/2012 11:46 AM, Koehne Kai wrote: >> -Original Message- >> From: development-bounces+kai.koehne=digia@qt-project.org >> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On >> Behalf Of Konstantin Tokarev >> Sent: Thursday, October 25, 2012 11:33 AM >> To: Thiago

Re: [Development] Android build

On 10/24/2012 12:16 PM, Łukasz Korbel wrote: > Hello, > > I have build Qt5 Beta following instructions from > http://qt-project.org/wiki/Android (with some small fixes for paths) > > I noticed that qt had built without QtDeclarative module, so I've built > it manually. > Its still not recognized as

Re: [Development] Stepping down as the maintainer of QtWayland

On 10/24/2012 05:50 PM, Hausmann Simon wrote: > +1 > > I've overheard Andy in hallway conversations where he switched occasionally > from English (accented) to the wayland protocol (1.0 final spec) and back. +1 from me as well :) -- Samuel ___ Develop

Re: [Development] Proposal: Change Qt's Security Policy to Full Disclosure

On 10/24/2012 11:30 AM, d3fault wrote: > On 10/24/12, Samuel Rødal wrote: >> Lars and Charles both provided good lists of reasons in another part of >> this thread for going with the policy of Responsible Disclosure. Clearly >> you disagree on the weighting of the pros and

Re: [Development] Proposal: Change Qt's Security Policy to Full Disclosure

On 10/24/2012 01:12 AM, d3fault wrote: > On 10/23/12, Lincoln Ramsay wrote: >> We're not renaming things or creating new lists just to match the >> names you think we should have. >> > > *sigh*, I had a feeling someone would say something like that. > > The changes are trivial at a glance, yes

Re: [Development] xcb-icccm dependency in Qt 5/libxcb

On 10/22/2012 01:53 PM, Koehne Kai wrote: > Hi, > > In Qt 5 we're relying on libxcb instead of the aging xlib. One drawback is > that it limits the portability of Qt binaries on Linux (AFAIK xcb isn't part > of any LSB). But it turns out the real dealbreaker when trying to have a > somewhat port

Re: [Development] renaming all QWindow properties that have "window" in them

On 10/19/2012 10:18 PM, Shawn Rutledge wrote: > On 19 October 2012 21:56, Oswald Buddenhagen > wrote: >> On Fri, Oct 19, 2012 at 04:46:01PM +, Rutledge Shawn wrote: >>> QWindow has properties like windowTitle, windowIcon, windowModality, >>> windowState and so on, which are named that way to

Re: [Development] renaming all QWindow properties that have "window" in them

On 10/19/2012 06:46 PM, Rutledge Shawn wrote: > QWindow has properties like windowTitle, windowIcon, windowModality, > windowState and so on, which are named that way to be familiar to users of > QWidget. However it causes some silliness in Qt Quick: QQuickWindow inherits > QWindow, and that me

Re: [Development] New high-dpi QPen proposal (Was Re: Proposal: Make QPen non-cosmetic by default)

On 10/18/2012 11:08 AM, Bache-Wiig Jens wrote: >> Maybe as a best effort we could introduce a different render hint, >> asking QPainter to treat cosmetic pens as geometric, would be a better >> solution for Morten's high-dpi use case. Then it would be opt-in instead >> of opt-out, and no existing a

[Development] New high-dpi QPen proposal (Was Re: Proposal: Make QPen non-cosmetic by default)

On 10/18/2012 07:53 AM, Uwe Rathmann wrote: > On Wed, 17 Oct 2012 16:47:00 +0200, Samuel Rødal wrote: > >> Seems to me to be the best compromise to avoid completely breaking too >> much existing code. > > I don't agree - it is going to break many applications doing gr

Re: [Development] Proposal: Make QPen non-cosmetic by default

On 10/15/2012 08:30 PM, Uwe Rathmann wrote: > On Mon, 15 Oct 2012 07:32:52 +, Knoll Lars wrote: > >> to make it really logical would probably also require to >> make 0 width pens invisible > > You are hitting the point: obviously setting a pen width of 0 enables a > special mode and doesn't rea

Re: [Development] Proposal: Make QPen non-cosmetic by default

On 10/11/2012 02:22 PM, Sorvig Morten wrote: > > On Oct 11, 2012, at 10:58 AM, Bache-Wiig Jens > 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)

Re: [Development] Proposing Shawn Rutledge as approver

On 10/16/2012 01:52 PM, Frederik Gladhorn wrote: > Hello, > > I'd like to propose Shawn for approver status. Seconded, a +1 from me as well. -- Samuel ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/

Re: [Development] Proposal: Make QPen non-cosmetic by default

On 10/11/2012 10:58 AM, Bache-Wiig Jens wrote: > This issue came up while preparing some code to be High-dpi aware but it is > really a completely separate issue. > While I previously supported the idea that cosmetic pens should be two pixels > wide by default on HDPI screens, I think we should t

Re: [Development] Proposal: Make QPen non-cosmetic by default

On 10/15/2012 09:36 PM, Uwe Rathmann wrote: > On Mon, 15 Oct 2012 09:58:20 +0200, Samuel Rødal wrote: > >> Could you elaborate on what you mean regarding the implementation of the >> subsurfaces concept? > > This is an experience from a project I'm working on: >

Re: [Development] Proposal: Make QPen non-cosmetic by default

On 10/15/2012 08:30 PM, Uwe Rathmann wrote: > On Mon, 15 Oct 2012 07:32:52 +, Knoll Lars wrote: > >> to make it really logical would probably also require to >> make 0 width pens invisible > > You are hitting the point: obviously setting a pen width of 0 enables a > special mode and doesn't rea

Re: [Development] status and use cases for QScreen

On 10/12/2012 10:24 PM, Shawn Rutledge wrote: > On 12 October 2012 21:03, Lorn Potter wrote: >> On 13/10/2012, at 12:47 AM, Shawn Rutledge >> wrote: >> >>> I got started working on QScreen, its properties, notifiers, and >>> implementation on all 3 platforms after I noticed that the >>> document

Re: [Development] Proposal: Make QPen non-cosmetic by default

On 10/12/2012 08:18 PM, Uwe Rathmann wrote: > Qt/Embedded is the platform where you find this type of widget most what > usually means a combination of the weakest hardware and the slowest > graphic path. Unfortunately the implementation of the subsurfaces concept > is so very broken, that embeddin

Re: [Development] Proposal: Make QPen non-cosmetic by default

On 10/12/2012 03:17 PM, Uwe Rathmann wrote: > On Fri, 12 Oct 2012 12:21:30 +, Bache-Wiig Jens wrote: > >> After all what is the point of doing a >> major version unless we don't even allow ourselves to change broken >> defaults. > > There is nothing broken: it's a well defined API that behaves

[Development] Behavior change: A sane and consistent QPainter coordinate system in Qt 5

While we're on the topic of pixels, in Qt 4 we in effect have two coordinate systems. The antialiased coordinate system where (0, 0) corresponds to the top left corner of the top left pixel, and the aliased coordinate system where (0, 0) corresponds to the center of the top left pixel. That mea

Re: [Development] High-dpi Qt best practices

On 10/11/2012 10:16 AM, Sorvig Morten wrote: > > On Oct 11, 2012, at 9:36 AM, Samuel Rødal > 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

Re: [Development] High-dpi Qt best practices

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 really want to > take advantage of each and every pixel in e.g. painting c

Re: [Development] High-dpi Qt best practices

On 10/09/2012 01:53 PM, Olivier Goffart wrote: > On Tuesday 09 October 2012 10:50:26 Sorvig Morten wrote: >> On Oct 9, 2012, at 12:21 PM, Olivier Goffart >> Pixmaps and images _always_ have exactly QPixmap::size() pixels. >> >>> Maybe we can introduce QSizePt >>> Code would look like >>> QPixmap p

Re: [Development] Antialiasing

On 10/05/2012 02:28 PM, Wehmer, Matthias wrote: > Hi Samuel, > > I will try to make myself clearer, sorry for that unclear information. > > The shaders I’m talking about are those, that I implemented in my custom > Qml plugin via the QSGSimpleMaterial class. There I have implemented two > custom ve

Re: [Development] Antiaaliasing

On 10/05/2012 11:57 AM, Wehmer, Matthias wrote: > Hi everybody, > > I need some information regarding the antialiasing functionality in Qt > 5. I have implemented a custom widget which basically draws a lot of > lines (also uses custom materials). Unfortunately they are not at all > AA. Anyway, via

Re: [Development] resolution independence (was Re: Retina display support)

On 10/03/2012 02:24 PM, Shawn Rutledge wrote: > On 3 October 2012 12:12, Samuel Rødal wrote: >> On 10/02/2012 01:58 PM, Atlant Schmidt wrote: >>> Samuel: >>> >>>> Specifying that all characters must be 5mm in physical height is >>>> typically not

Re: [Development] resolution independence (was Re: Retina display support)

On 10/02/2012 01:58 PM, Atlant Schmidt wrote: > Samuel: > >> Specifying that all characters must be 5mm in physical height is >> typically not what a UI wants in any case, since different types of >> displays (mobiles / tablets, computer monitors, and TVs) are typically >> viewed at different dista

Re: [Development] resolution independence (was Re: Retina display support)

On 10/03/2012 12:10 AM, Andreas Holzammer wrote: > I can only add that the reported physical dpi for windows are not the > real physical. They report what the user has set in windows for it, or > better to say it defaults to 96 dpi. There seems to be no api from > windows to find out the actual ap

Re: [Development] resolution independence (was Re: Retina display support)

On 10/01/2012 01:52 PM, Atlant Schmidt wrote: > Folks: > > > Likewise the idea that HiDPI displays are always "2x" seems to me another > > inelegant hack. Actually the DPI varies between devices, so > high-resolution > > art should not always need to be exactly 2x the normal size. It may be >

Re: [Development] Accelerated/OpenGL drawing under Qt 5.0

On 09/14/2012 04:18 PM, ext Chris Meyer wrote: > On Fri, Sep 14, 2012 at 2:49 AM, Samuel Rødal wrote: >> On 09/12/2012 06:52 AM, ext Chris Meyer wrote: >>> My software makes use of accelerated drawing using the techniques with >>> QGraphicsView and QGraphics

Re: [Development] Accelerated/OpenGL drawing under Qt 5.0

On 09/12/2012 06:52 AM, ext Chris Meyer wrote: > My software makes use of accelerated drawing using the techniques with > QGraphicsView and QGraphicsScene shown in this article: > > http://doc.qt.nokia.com/qq/qq26-openglcanvas.html > > Unfortunately things don't work smoothly under Qt 5.0. > > I

Re: [Development] Accelerated/OpenGL drawing under Qt 5.0

On 09/12/2012 04:33 PM, ext Chris Meyer wrote: > On Tue, Sep 11, 2012 at 9:52 PM, Chris Meyer wrote: >> My software makes use of accelerated drawing using the techniques with >> QGraphicsView and QGraphicsScene shown in this article: >> >> http://doc.qt.nokia.com/qq/qq26-openglcanvas.html >> >> Un

Re: [Development] About QML depends on opengl

On 09/04/2012 09:38 AM, ext song.7@nokia.com wrote: > Hi, > > We are trying to port the mesa. But there is one question related with OpenGL. Not sure trying to port Mesa to a 300 MHz device is going to give you acceptable performance. Softpipe would use many seconds to render a single frame,

Re: [Development] About QML depends on opengl

On 09/04/2012 09:38 AM, ext song.7@nokia.com wrote: > Hi, > > We are trying to port the mesa. But there is one question related with OpenGL. > > In Linux, we can create OpengGL context using glXCreateContextAttribsARB, > then glXMakeCurrent will binding this context to a window. > But we don

Re: [Development] Qt 5.0 Beta Performance

On 09/03/2012 09:42 AM, ext Samuel Rødal wrote: > On 08/31/2012 02:05 AM, ext David Boosalis wrote: >> I download the latest beta version of Qt 5.0 onto my Linux box (Kubuntu >> 12.04) . For a beta it looks real good, but one thing I found >> concerning was the performance.

Re: [Development] Qt 5.0 Beta Performance

On 08/31/2012 02:05 AM, ext David Boosalis wrote: > I download the latest beta version of Qt 5.0 onto my Linux box (Kubuntu > 12.04) . For a beta it looks real good, but one thing I found > concerning was the performance. I mean even running the demo "samegame" > take over 98% of my cpu. Being th

Re: [Development] About copying the image buffer with alpha blending

On 08/29/2012 09:53 AM, ext song.7@nokia.com wrote: > Hi, > > > > We found that QPainer::drawImage takes 30~50ms for one 150*114 image, it > seems a little slow. > > > > One quick optimization to try is: we want to do the memory copy to the > backing store buffer directly instead of usi

Re: [Development] Question regarding commit: Fix transformation in eglfs backingstore

On 08/28/2012 08:31 AM, ext laszlo.p.ag...@nokia.com wrote: > Ok, let's just revert the change if it breaks on Pi. It wouldn't make much of > a difference on eglfs anyways due to the forced-fullscreen windows. > > The change originates from kms which, due to the way it is currently > implemented

Re: [Development] OpenGL Support in Qt5

On 07/23/2012 12:25 PM, Knoll Lars (Nokia-MP/Oslo) wrote: > On 7/23/12 10:55 AM, "ext Samuel Rødal" wrote: > >> On 07/16/2012 10:59 PM, ext Fredrik Höglund wrote: >>> On Monday 16 July 2012, Thiago Macieira wrote: >>>> On segunda-feira, 16 de julho de

Re: [Development] OpenGL Support in Qt5

On 07/16/2012 10:59 PM, ext Fredrik Höglund wrote: > On Monday 16 July 2012, Thiago Macieira wrote: >> On segunda-feira, 16 de julho de 2012 07.47.10, gunnar.sle...@nokia.com >> wrote: >>> I both like and dislike the idea. Like because it resolves all the functions >>> and that way save a lot of p

Re: [Development] QtCS: OpenGL session notes

On 07/02/2012 02:57 PM, ext Keith Gardner wrote: > Why don't you make an OpenGL middleware driver? Then your application will > always be an OpenGL application and the middleware driver will take all of > the OpenGL calls in place of the system's driver and do the translation > there? The midd

Re: [Development] QtCS: OpenGL session notes

On 06/28/2012 01:46 PM, Storm-Olsen Marius (Nokia-MP/Austin) wrote: > On 28/06/2012 01:59, ext Samuel Rødal wrote: >> On 06/27/2012 06:30 PM, ext marius.storm-ol...@nokia.com wrote: >> In theory we could even support both options in the windows platform >> plugin, and choos

Re: [Development] QtCS: OpenGL session notes

On 06/27/2012 06:30 PM, ext marius.storm-ol...@nokia.com wrote: > On 25/06/2012 13:44, ext Girish Ramakrishnan wrote: >> Future plans >> - Desktop OpenGL 3+ support, ES 3 support > > We've just added ANGLE support in Qt (-angle ), to enable DirectX > usage instead of OpenGL ES 2 on Windows, due t

Re: [Development] QtCS: OpenGL session notes

On 06/26/2012 09:29 AM, ext Joe Yu wrote: > Hi, > > Is there anybody knows how to enable OpenGL (or OpenGL ES) as QPainter's > backend? I learned from some document there's an existing OpenGL/GLES > backend in QPainter. > > Thanks, > Joe Yu You'll get the OpenGL backend as long as you're paintin

Re: [Development] Another late API addition in QScreen

On 06/06/2012 03:38 PM, ext shane.kea...@accenture.com wrote: >> -Original Message- >> From: development-bounces+shane.kearns=accenture@qt-project.org >> [mailto:development-bounces+shane.kearns=accenture@qt-project.org] >> On Behalf Of Samuel Rødal >

Re: [Development] pushes to gerrit failing

On 06/06/2012 01:59 AM, ext Girish Ramakrishnan wrote: > Hi CI team/Gerrit team, > Pushes to gerrit are failing (qtbase). Not just for Girish, happens here as well. > girish@beast:~/Qt/qt5/qtbase$ git push gerrit HEAD:refs/for/master > Counting objects: 12, done. > Delta compression using up to 6

  1   2   >