Re: [Development] FOSDEM Desktops DevRoom 2016: Call for Participation

Hello, Just a quick mail to remind everybody we will accept talk proposals for the Desktops DevRoom at FOSDEM 2016 only until this Saturday. Hurry up! On Mon, Nov 2, 2015 at 8:44 PM, Pau Garcia i Quiles wrote: > > FOSDEM Desktops DevRoom 2016 Call for Participation > >

[Development] About qfilesystemwatcher: what events?

Hi, I'm looking at qfilesystemwatcher. It's not possible to configure what events it watches. For example: when watching a directory and an event happens on an entry in this directory: it's changed. The size for example is changed. qfilesystemwatcher doe not give this information: it only

[Development] https://bugreports.qt.io/browse/QTBUG-48717 - need help

I need someone with an ARM board to reproduce the issue and pinpoint where the event delivery problem might be. My gut feeling was that it was caused by the different platform plugins, my the reporter says that the problem happens with XCB too. There should be no platform-specific code in the

[Development] buildsystem now needs to keep behaviour compatibility

[This is mostly to Ossi, Jörg and myself, but sending to everyone FYI] Now that we will no longer include qtwebkit, qtquick1 and qtscript in the main releases, we are asking people to continue building the last released version of some of those modules against newer Qt versions. That was in the

Re: [Development] About qfilesystemwatcher: what events?

Hi, I will look into it. Do I have to checkout the qt source as described here: http://wiki.qt.io/Building_Qt_5_from_Git Futher is there a projectpage? (to see the current issues) And is the ability to forward a watch to a network filesystem included? Please let me explain. I've been digging

Re: [Development] https://bugreports.qt.io/browse/QTBUG-48717 - need help

On Monday 30 November 2015 09:02:55 Thiago Macieira wrote: > I need someone with an ARM board to reproduce the issue and pinpoint where > the event delivery problem might be. My gut feeling was that it was caused > by the different platform plugins, my the reporter says that the problem > happens

Re: [Development] QtCS: Notes from Modern C++ session

On Tuesday 16 June 2015 22:31:51 Thiago Macieira wrote: > MSVC 2012 and 2013 have a parsing bug with them, so you need to > compile your code with one of those two versions if you're introducing new > range fors. Do you have specifics here? IIRC, it was something like while (...)

Re: [Development] About qfilesystemwatcher: what events?

On Mon, Nov 30, 2015 at 11:07 AM, Stef Bon wrote: > Hi, > > I'm looking at qfilesystemwatcher. > It's not possible to configure what events it watches. For example: > > when watching a directory and an event happens on an entry in this > directory: it's changed. > The size for

Re: [Development] Suggestion for change on how blockers are marked in Jira

On 27. nov. 2015 14:53, Paul Olav Tvete wrote: On Friday, November 27, 2015 02:23:01 PM Eskil A. Blomfeldt wrote: I think a batched change for all open reports with a "Fix version" != "Some future release" would have to be part of this. A quick check reveals that we (for instance) currently

Re: [Development] Suggestion for change on how blockers are marked in Jira

On 30/11/15 13:13, "Development on behalf of Eskil A. Blomfeldt" wrote: > > >On 27. nov. 2015 14:53, Paul Olav Tvete wrote: >> On Friday, November 27, 2015 02:23:01 PM Eskil A. Blomfeldt wrote: >>> I

Re: [Development] Suggestion for change on how blockers are marked in Jira

On 27. nov. 2015 14:42, Blasche Alexander wrote: -Original Message- From: Development [mailto:development-boun...@qt-project.org] On Behalf Of Christian Kandeler ... Sounds sensible, but what about all the existing bugs that have a "Fix version" assigned? Won't they all become