I’m having some trouble with Component::beginDragAutoRepeat() after updating the version of the tip I’m building against. I have a custom component that calls Compononent::beginDragAutoRepeat( ) in its mouseDrag callback. When I was building against a version of the tip from around September of last year, this worked fine. After a recent update the beginDragAutoRepeat( ) doesn’t appear to have any affect on the mouse dragging.
I see that there were a lot of changes to the internal mouse handling code in JUCE since the old version of the tip I was using. In the debugger I see that beginDragAutoRepeat( ) eventually calls MouseInputSource::triggerFakeMove( ), which pushes an asynchronous message onto the message thread. From that point on I’m a little lost as to what is going on. After the fake mouse move message has been posted, I don’t see any mouse events or mouse drag callbacks being fired. Component::internalMouseDrag( ) is never called, for example. When I step through the debugger using the older JUCE tip it’s very clear that
beginDragAutoRepeat( ) eventually calls internalMouseDrag( ), which calls my custom component’s mouseDrag callback and starts the cycle again.
I’m not sure how or where the mouse event should being generated in the new version of the JUCE tip, or if it is being generated at all. Any insight on how this is supposed to work would be greatly appreciated.