No response to mouse in DemoRunner with heavy animation

Hi,

Using JUCE 8 on Windows (so with the direct2d backend), I’m getting issues with mouse / keyboard interaction when there is an heavy animation.

It can be reproduced easily with the DemoRunner WindowsDemo, just increase the number of bouncing balls to a larger value, such as 600, and reduce the timer interval of BouncingBallComponent from 60 to 4.

The animation of the bouncing balls is displayed very smoothly, but the application does not respond to any mouse event (if it still does, just increase the number of bouncing balls). Even clicking on the main DemoRunner titlebar in order to drag the application does nothing. The only option is to kill the app.

I’m testing with an up-to-date develop branch.

I was just talking to another developer about this exact issue. I’ll post more about it soon.

Matt

We urgently need a fix/workaround for that as well.

Apologies for the lack of communication. It’s a problem, we’re working on it, but we don’t have anything concrete to report at the moment.

Hi, what is the status for this issue ? I notice it is still there (on latest develop branch).

The latest ideas from @matt need to be incorporated to avoid saturating the windows message queue.

He has a JUCE branch you could try:

Still sorting out a few issues.

Matt

I have updated today to latest JUCE develop branch and despite the numerous Direct2D related patches that have been pushed recently, the responsivity issue is still there, unfortunately.

I’ll take a look.

Matt

Thanks – the ui does not freeze completely anymore, but the reaction to mouse events is lagging by like 0.5 seconds. Very noticeable when dragging the DemoRunner windows (native or juce one).

I can reproduce this. We might still need some kind of frame rate limiter.

Matt

1 Like