Sure, with the removal I only meant the xsm implementation :)
Simon
Original Message
From: Samuel Gaist
Sent: Thursday, April 30, 2015 23:36
To: Hausmann Simon
Cc: Matthew Woehlke; development@qt-project.org; releas...@qt-project.org
Subject: Re: [Development] Qt 4.8.7 release candidate availa
There are some cases when non-standard keys should be handled. Remote
control units with custom key codes are the primary example. Existing Keys
QML type provides a handy means of processing specific key events only for
a small subset of Qt::Key enum, and that is true only for presses, not
release
Hi,
It's back since 5.2 with an implementation for OS X waiting for Qt 5 (also for
Qt 4 but since it's considered a new feature it won't get in)
Samuel
On 30 avr. 2015, at 19:37, Hausmann Simon
wrote:
> IMO this isn't a Qt bug, I commented on Jira.
>
> I suspect another app isn't implementi
On 2015-02-20 14:42, Thiago Macieira wrote:
> On Friday 20 February 2015 12:53:24 Matthew Woehlke wrote:
>> for (auto const i : qtEnumerate(map))
>>
>> Maybe it would be nice for Qt to provide one or both of these?
>
> Sounds easy enough. Want to give it a try?
I *finally* got permission to sha
IMO this isn't a Qt bug, I commented on Jira.
I suspect another app isn't implementing the protocol directly, but if we
really want to protect ourselves then we should probably ditch the entire
session management code from Qt 4 (it's gone in Qt 5, too :)
Simon
Original Message
From: Matthew
On 2015-04-30 09:17, Salovaara Akseli wrote:
> If blocker issues for Qt 4.8.7 release (i.e. new regression) are found please
> report those to bugreports.qt.io and raise issue also (with bug id) on
> releasing mailing list.
Is there no hope for getting https://bugreports.qt.io/browse/QTBUG-38599
Hi,
Qt 4.8.7 release candidate packages are available at
http://download.qt.io/development_releases/qt/4.8/4.8.7-rc1/ and SHA-1 is now
frozen so please test these packages accordingly.
These packages are built against SHA-1:
fa81aa6d027049e855b76f5408586a288f160575 * QNAM: Fix upload corruptio
Makes sense, thanks.
R
On 29 Apr 2015, at 12:35, Ziller Eike wrote:
>
>> On Apr 21, 2015, at 11:46 AM, René J.V. Bertin wrote:
>>
>> Hi,
>>
>> I know I should ask this on the QC ML (but I'd prefer not to sign up for
>> just an occasional question like this):
>>
>> Is there a (good) reason
On Thursday, April 30, 2015 10:50:59 AM Marc Mutz wrote:
> > > 2. what business does a program have, anyway, of modifying the
> > >
> > >environment after threads may have started? Such code should be
> > >fixed.
> > >Making the Qt wrappers "save" could lead to more code doing nonsense
On Wednesday 29 April 2015 11:15:21 Simon Hausmann wrote:
> > 1. man putenv on Linux says that since glibc 2.1, putenv is reentrant. In
> >
> >any case, it's almost trivial to fix this in libc (using CAS, as Ossi
> >suggested in a comment on v1 of the patch), but impossible outside.
>
> Do
10 matches
Mail list logo
