On Friday November 07 2014 23:09:16 Andreas Pakulat wrote:
Hi again,
> Not necessarily, or at least not necessarily user input events in the same
> process/application. For example think about a user moving a window over
That's what I meant, they may not result from direct interaction with the
Hi,
On Fri, Nov 7, 2014 at 5:09 PM, René J.V. wrote:
> On Friday November 07 2014 16:49:21 Andreas Pakulat wrote:
>
> Hi
>
> >Let me clarify something since you're always talking about UI events, but
>
> I should clarify something too: the 1st crash report I linked to was not
> due to me access
Thanks, Sean.
I have not seen any behavior problems associated with the warning. We actually
see the warning on Windows more than on Macintosh. On Windows we run in an MDI
window. In certain cases we need a winID in order to wrap native GUI elements
(we allow customers to create plugins with wi
Hi,
On Fri, Nov 7, 2014 at 2:41 PM, René J.V. wrote:
> On Friday November 07 2014 14:16:07 Andreas Pakulat wrote:
> > even if the dbus message is triggered through a user event (like clicking
> > in the menubar or so) thats not possible for Qt to see anymore since a
> dbus
> > event may also com
It has nothing to do with paint speed, it’s just an animation effect applied
when the highlight item changes, you should try to set the
highlightResizeDuration and highlightResizeVelecity property.
___
Interest mailing list
Interest@qt-project.org
http:
On Friday November 07 2014 14:16:07 Andreas Pakulat wrote:
> I don't see any user input events there either. The crash is triggered from
> an invokeMethod call which seems to be triggered from a dbus connection. So
Ah, yes, that's quite possible. A debugging nightmare, that whole DBus thing ...
Hi,
On Fri, Nov 7, 2014 at 1:12 PM, René J.V. wrote:
> On Friday November 07 2014 12:44:27 Andreas Pakulat wrote:
> >Looking at that backtrace I don't see UserInput events. At least
> >QTimerInfoList::activateTimers suggests a QTimer fires, thats not a
> >UserInput nor a UserInterface event.
>
>
Hi,
On Fri, Nov 7, 2014 at 11:10 AM, René J.V. wrote:
> I'm using KDE's KMail on Linux and Mac OS X, and I've been dealing with
> crashes on both platform when UI events "come through" during the shutdown
> phase.
>
> Specifically, KMail's cleanup procedure runs a few so-called KJobs (a
> class
On 7 Nov 2014, at 02:05, John Weeks wrote:
> Can anyone tell me about QWindow::setTransientParent()? When building with
> Qt 5 I keep seeing warnings:
>
> void QWindow::setTransientParent(QWindow *) QWidgetWindow(0x118c39a10, name =
> "QWidgetClassWindow") must be a top level window.
>
> On
