Re: [Development] MouseArea: updating hover state when the area moves

On Tue, Aug 20, 2013 at 6:15 AM, Josh Faust wrote: >I'm curious what the reasoning behind this is. Is it just a performance >optimization? I think so. Currently scene items don't get a notification if their absolute positioning changes while the relative position to the parent does not. See http:

Re: [Development] Windows: Building QtCore without ICU while still using it for QtWebKit?

> -Original Message- > From: development-bounces+kai.koehne=digia@qt-project.org > [mailto:development-bounces+kai.koehne=digia@qt-project.org] On > Behalf Of Josh Faust > Sent: Tuesday, August 20, 2013 6:25 AM > To: development > Subject: [Development] Windows: Building QtCore wit

Re: [Development] QTBUG-30440: restricting the SIMD files

On 20.08.13 03:54, "Thiago Macieira" wrote: >On quinta-feira, 15 de agosto de 2013 08:06:19, Thiago Macieira wrote: >> > I'd agree that option (4) is the cleanest solution. Have you checked >>how >> > much we'd need to change to implement it? >> >> No, not yet. >> >> I don't think it will be

[Development] Windows: Building QtCore without ICU while still using it for QtWebKit?

Is there any way to avoid the ICU dependency in QtCore while still building QtWebKit with it? My use-case is thus: * Externally shipping application that does not use QtWebKit, and does not use ICU * Internal tools that do use QtWebKit We'd love to avoid the ICU dependency in the external appli

[Development] MouseArea: updating hover state when the area moves

>From the MouseArea docs: Warning: This property is not updated if the area moves under the mouse: containsMouse will not change I'm curious what the reasoning behind this is. Is it just a performance optimization? I ask as it makes a number of things not work properly when: * The window resize

Re: [Development] QTBUG-30440: restricting the SIMD files

On quinta-feira, 15 de agosto de 2013 08:06:19, Thiago Macieira wrote: > > I'd agree that option (4) is the cleanest solution. Have you checked how > > much we'd need to change to implement it? > > No, not yet. > > I don't think it will be too hard because those routines are still fairly > limit

Re: [Development] QStandardPath search paths

On segunda-feira, 19 de agosto de 2013 17:15:31, Alan Alpert wrote: > The discussion has moved on a bit since, but I don't think we really > answered this question (one person said "sounds good", before Thiago's > email). Asset paths are probably going to be treated slightly > differently now, but

Re: [Development] QStandardPath search paths

On Wed, Jul 31, 2013 at 10:55 AM, Thiago Macieira wrote: > On quarta-feira, 31 de julho de 2013 16:33:31, Hausmann Simon wrote: >> I wonder what Filesystem folks think about it (especially Andreas, who was >> around when I added the search dirs with Girish) > > My opinion is that the search path f

Re: [Development] Enabling -Werror developer builds

On Mon, Aug 19, 2013 at 4:47 PM, Thiago Macieira wrote: > On segunda-feira, 19 de agosto de 2013 15:40:06, Alan Alpert wrote: >> > 2) -Werror is enabled only for certain compiler versions. I'll update the >> > whitelist to have an upper range too. For example, right now it enables - >> > Werror fo

Re: [Development] AplicationWindow, QQuickWindow, contentRotation and setting width and height of contentItem

On Fri, Aug 2, 2013 at 11:49 AM, Tomasz Olszak wrote: >> You should also be able to work around it inside your >> ApplicationWindow by hiding the parent property on your content item. >> Something like "property Item parent: null" should make it look like >> the root of the tree. It's not great, b

Re: [Development] Enabling -Werror developer builds

On segunda-feira, 19 de agosto de 2013 15:40:06, Alan Alpert wrote: > > 2) -Werror is enabled only for certain compiler versions. I'll update the > > whitelist to have an upper range too. For example, right now it enables - > > Werror for GCC 4.6 and above. I'm going to introduce an upper limit > >

Re: [Development] Enabling -Werror developer builds

On Mon, Aug 19, 2013 at 3:14 PM, Thiago Macieira wrote: > Hello > > Commit ebfd85a499a4382ace09d443b1f35cd6b1848af6 adds support for -Werror, but > it hasn't been acted on yet. The commit says: > > This is enabled only for -developer-builds and only for certain > compiler-version combinati

Re: [Development] New JIRA type 'Feature'? (was RE: FW: Proposal for RFC like feature process)

On Wed, Aug 14, 2013 at 12:03 AM, Koehne Kai wrote: > Alright, discussion about a new JIRA type 'Feature' went on at > > https://bugreports.qt-project.org/browse/QTJIRA-233 > > with two different ideas: > > 1) That we already have too many issue types in JIRA, and adding another one > makes thin

Re: [Development] [Feature Request] Websockets

On 18/08/13 05:08, Matt Broadstone wrote: > On Sat, Aug 17, 2013 at 4:17 AM, Kurt Pattyn > wrote: > > Well, > > it is a fact that Qt has little to no native support for 'cloud' > based client and server 'protocols', like REST, WebSockets, SOAP, > aso.

[Development] Enabling -Werror developer builds

Hello Commit ebfd85a499a4382ace09d443b1f35cd6b1848af6 adds support for -Werror, but it hasn't been acted on yet. The commit says: This is enabled only for -developer-builds and only for certain compiler-version combinations that are in a whitelist. It also requires each library,

Re: [Development] QTBUG-30440: restricting the SIMD files

On segunda-feira, 19 de agosto de 2013 07:56:43, Koehne Kai wrote: > > We recommend people set the environment if they want different flags, > > besides the stock from their compilers. > > Where do we recommend this? E.g. > > http://qt-project.org/doc/qt-5.0/qtdoc/install-x11.html > > just says

Re: [Development] QTBUG-30440: restricting the SIMD files

On 2013-08-19 05:56, Knoll Lars wrote: > On 19.08.13 09:56, "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 Thiago Macieira Sent: Monday, August 19

Re: [Development] Unable to debug with Remote inspector

Hi Jocelyn, Thanks for your inputs. But I am not using webkit that comes along with Qt 4.8. I am pulling webkit directly from trunk and branched off with revision number 1,16,000. So with this webkit build on linux I am able to launch the remote inspector. But on windows I am facing problems. R

[Development] Qt5.1 Post Mortem

Hi, New minor release was done at the beginning of July and now it is time to collect some lessons learnt. I hope you would be willing to give us your feedback on the release related work for Qt5.1. I know there was this same action done for Qt5.0 and I am hoping at least something has gone

Re: [Development] Using QCollator on different platforms, without ICU

On Tue, Aug 13, 2013 at 7:50 PM, Aleix Pol wrote: > Hi, > So since we're a bit stuck on that area, I guessed that it would be a good > idea to start to get our hands dirty. > > I started an approximation to the project by implementing the different > API bits using the different platforms native

[Development] Unable to debug with Remote inspector

Hi Group, I have a QWebview application(I am using Qt 4.8.x) using which I launch a test URL(Test html app). Now I am trying to use remote inspector to debug the html application using http://localhost: from chrome browser. When I do this, I get the link to URL which was launched u

Re: [Development] QTBUG-30440: restricting the SIMD files

On segunda-feira, 19 de agosto de 2013 07:37:58, Koehne Kai wrote: > I don't know how big the performance gains really are, but if it's > noticeable, why not switch the default for everyone using the default > mkspec? Switching the default means making it difficult to unset for those who want it