On 12/30/2013 01:49 PM, Andreas Aardal Hanssen wrote:
> Why keep the breakage though. This fix would still require a note in
> porting docs and changes to code. Why fix what was never broken - just
> go back to Qt 4 behavior..
Hi, Andreas. Please note that the Bug Report, QTBUG-25831, is re-opened,
Why keep the breakage though. This fix would still require a note in
porting docs and changes to code. Why fix what was never broken - just
go back to Qt 4 behavior..
Sorry for the post format, crap mail client issue...
___
Development mailing list
Devel
On 12/30/2013 12:50 AM, Rutledge Shawn wrote:
> On 23 Dec 2013, at 5:37 PM, Rick Stockton wrote:
>
>> QTBUG-25831 is re-opened, and assigned to me. The linked gerrit change
>> would "solve" the problem for Widgets- creating the issue
>> Shawn Rutledge has suggested making the change configurable
On 23 Dec 2013, at 5:37 PM, Rick Stockton wrote:
> QTBUG-25831 is re-opened, and assigned to me. The linked gerrit change
> would "solve" the problem for Widgets- creating the issue that a LOT of
> Qt5 modules are listening only for single-click, and would now need to
> listen for both events if
QTBUG-25831 is re-opened, and assigned to me. The linked gerrit change
would "solve" the problem for Widgets- creating the issue that a LOT of
Qt5 modules are listening only for single-click, and would now need to
listen for both events if they need to respond properly to a big
sequences of fast si
On 12/20/2013 02:05 AM, Martin Koller wrote:
> On Thursday 19 December 2013 22:18:36 Andreas Aardal Hanssen wrote:
>> On 19 Dec 2013, at 18:36, Rick Stockton
>> wrote:
>>> Perhaps we should perform as QT4 did (there wasn't a second ButtonPress,
>>> the DoubleClick "ate it"). Such use cases would
On Thursday 19 December 2013 22:18:36 Andreas Aardal Hanssen wrote:
>
> On 19 Dec 2013, at 18:36, Rick Stockton
> wrote:
> > Perhaps we should perform as QT4 did (there wasn't a second ButtonPress,
> > the DoubleClick "ate it"). Such use cases would then need to be "fixed
> > up" (i,e, to accept
On 20 Dec 2013, at 09:15, Martin Koller wrote:
> so it's just the extra mousePressEvent in Qt5 which is wrong.
Good. I think it can and should just be removed, but it would be nice to know
when it broke, in case there was thought behind it...
Andreas_
On Friday 20 December 2013 08:31:24 Martin Koller wrote:
> On Thursday 19 December 2013 09:19:38 Rick Stockton wrote:
> > On 12/18/2013 01:10 PM, Andreas Aardal Hanssen wrote:
> > > On 18 Dec 2013, at 22:07, Rayner Pupo Gómez wrote:
> > Inner-most quote is from Martin Koller.
> >
> > >>> I've dis
On Thursday 19 December 2013 09:19:38 Rick Stockton wrote:
> On 12/18/2013 01:10 PM, Andreas Aardal Hanssen wrote:
> > On 18 Dec 2013, at 22:07, Rayner Pupo Gómez wrote:
> Inner-most quote is from Martin Koller.
>
> >>> I've discovered that with Qt5 I get a different order of mouse events on
> >>
On 19 Dec 2013, at 18:36, Rick Stockton
wrote:
> Perhaps we should perform as QT4 did (there wasn't a second ButtonPress,
> the DoubleClick "ate it"). Such use cases would then need to be "fixed
> up" (i,e, to accept EITHER event as a cause for executing that Action)?
> Logical, but a lot of wor
<< SNIP >>
On 12/18/2013 06:30 PM, Nicolás Alvarez wrote:
> 2013/12/18 Andreas Aardal Hanssen :
>> On 18 Dec 2013, at 22:07, Rayner Pupo Gómez wrote:
>>
I've discovered that with Qt5 I get a different order of mouse events on
a QWidget than with Qt4 (openSuse 13.1 Linux, X11):
doubl
On 12/18/2013 01:10 PM, Andreas Aardal Hanssen wrote:
> On 18 Dec 2013, at 22:07, Rayner Pupo Gómez wrote:
Inner-most quote is from Martin Koller.
>>> I've discovered that with Qt5 I get a different order of mouse events on
>>> a QWidget than with Qt4 (openSuse 13.1 Linux, X11):
>>> double clicki
On 19 Dec 2013, at 03:30, Nicolás Alvarez wrote:
> That would break many use cases, such as QSpinBox, which performs an
> action on every press (not release) and doesn't care about double
> click events.
No it wouldn’t. The default implementation of mouseDoubleClickEvent() calls
mousePressEvent(
2013/12/18 Andreas Aardal Hanssen :
> On 18 Dec 2013, at 22:07, Rayner Pupo Gómez wrote:
>
>>> I've discovered that with Qt5 I get a different order of mouse events on
>>> a QWidget than with Qt4 (openSuse 13.1 Linux, X11):
>>> double clicking a widget results in Qt4 in:
>>> mousePressEvent
>>> mo
On 18 Dec 2013, at 22:07, Rayner Pupo Gómez wrote:
>> I've discovered that with Qt5 I get a different order of mouse events on
>> a QWidget than with Qt4 (openSuse 13.1 Linux, X11):
>> double clicking a widget results in Qt4 in:
>> mousePressEvent
>> mouseReleaseEvent
>> mouseDoubleClickEvent
> I've discovered that with Qt5 I get a different order of mouse events on
> a QWidget than with Qt4 (openSuse 13.1 Linux, X11):
> double clicking a widget results in Qt4 in:
> mousePressEvent
> mouseReleaseEvent
> mouseDoubleClickEvent
> mousePressEvent
> mouseReleaseEvent
> but in Qt5 in:
> m
On 12/18/2013 07:16 AM, Martin Koller wrote:
> I've discovered that with Qt5 I get a different order of mouse events on
> a QWidget than with Qt4 (openSuse 13.1 Linux, X11):
> double clicking a widget results in Qt4 in:
> mousePressEvent
> mouseReleaseEvent
> mouseDoubleClickEvent
> mousePressE
I've discovered that with Qt5 I get a different order of mouse events on
a QWidget than with Qt4 (openSuse 13.1 Linux, X11):
double clicking a widget results in Qt4 in:
mousePressEvent
mouseReleaseEvent
mouseDoubleClickEvent
mousePressEvent
mouseReleaseEvent
but in Qt5 in:
mousePressEvent
mous
19 matches
Mail list logo
