Hello,
while investigating session saving problems in KDE I found that the big
underlying problem is that QGuiApplication::commitData() can't be
prevented from trying to close windows. It does that to see if they
refuse (ignore the close event), and if they do, it's interpreted as the
Ok, many thanks for the info. I have no more any questions. :)
BR,
Denis
2016-01-29 15:48 GMT+03:00 Eskil A. Blomfeldt <
eskil.abrahamsen-blomfe...@theqtcompany.com>:
>
>
> On 28. jan. 2016 10:46, Denis Shienkov wrote:
>
> Hi Qt developers.
>
> During a long time I see that a development of
Op 28/01/2016 om 13:00 schreef Maximilian Hrabowski:
Why isn't this first ?
I would generally expect an environment variable to take precedence over
all other configuration options except command-line options.
You are right, that an environment variable should be considered first. But I
You're right, the can is open right now. Apple is working on closing that can
under our feet (see the DYLD_* variable unsetting upon exec in 10.11). I
wouldn't be surprised if that trend continues elsewhere :)
Simon
From: Development
On Thursday 28 of January 2016 12:37:14 Hausmann Simon wrote:
> Regarding the server that is used for Qt 5.6 and onwards: It is an exact
> clone of the virtual machine that ran in Jenkins with no changes to the
> services, but it is in a different virtual network segment.
It is exactly the same,
On Friday 29 January 2016 14:45:06 Simon Hausmann wrote:
> Judging from responses on the internet like
[...]
> I have the impression that the Media Foundation in Windows does not support
> h264 payloads in RTSP. Not sure there's much we can do on the Qt side about
> that :)
Would it be possible
Judging from responses on the internet like
https://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/4ac87f5f-b8c5-471a-a424-55c0fff04eac/using-the-media-foundation-sdk-to-parse-rtsp-streams?forum=mediafoundationdevelopment
I have the impression that the Media Foundation in Windows does
On 28. jan. 2016 10:46, Denis Shienkov wrote:
Hi Qt developers.
During a long time I see that a development of QtMultimedia module is
stalled... Tons of bugs are not considered at all, and a code-review
commits keeps in reviews at monts without touching/response...
Besides, many of
> -Original Message-
> From: Development [mailto:development-boun...@qt-project.org] On
> Behalf Of Andre Somers
> Sent: Friday, January 29, 2016 9:05 AM
> To: development@qt-project.org
> Subject: Re: [Development] Modify QLibraryInfo to support any default
> location of qt.conf
>
>
>
On Friday 29 January 2016 10:42:17 Hausmann Simon wrote:
> You're right, the can is open right now. Apple is working on closing that
> can under our feet (see the DYLD_* variable unsetting upon exec in 10.11).
> I wouldn't be surprised if that trend continues elsewhere
ld-linux.so ignores the
On Friday 29 January 2016 14:54:59 Andreas Hartmetz wrote:
> So, how to fix it? Simple and (very) ugly: Add API to disable the
> closing of windows in commitData(). Because session saving is IMHO
> pretty important for KDE, I'm asking for an exception to add API to 5.6
> to fix it.
The API isn't
On Fri, Jan 29, 2016 at 9:08 PM, mark diener wrote:
>
> Tried to follow http://wiki.qt.io/Qt_Contribution_Guidelines but I am
> getting slammed by git/gerrit errors and some sort of commit hook.
If you can get online on IRC (Freenode, #qt-labs) you may find people
to help
On Friday 29 January 2016 14:08:31 mark diener wrote:
> The best I can hope to do is submit skeleton code pre-feature freeze
> with No-op code and then
> fill in the rest once I can spend some quality time on all of the tool
> chain configuration.
That's not acceptable for feature freeze.
All
13 matches
Mail list logo