No joy yet (though I’ve been doing other things as well).
It’s baffling - I can’t see how my program’s state would have changed by resizing it a little, but its window reliably won’t be dragged around until I resize it a tiny bit, and then it drags perfectly well.
It seems to me from setting my breakpoint at JuceNSView::frameChanged that I’ve pretty well ensured that it’s not that some event is being ignored, but that no event is being created in the first place when I try to drag the window around.
QUESTION ONE: What is it that generates these messages? Is some of that Juce or is it all in the OS? Is there somewhere in this stack that I could set a breakpoint?!
This is more or less all that keeps me from releasing my beta (except for some cosmetic issues) so I’m sort of eager to make some progress at least on this.
I’m going to do something horrible later today, which is to spawn off a thread that slightly resizes the main window after a few hundred milliseconds. I doubt this will do anything, as I’m already successfully persisting the size of the main window, so I know that I’m setting the size during the startup process - but perhaps doing it later will break the stuckness somehow…
But that’s not a good solution.
QUESTION TWO: if you were trying to get this effect of an unmoveable window, how would you do so, if you didn’t want to override moved and reset the Window’s size?
QUESTION THREE: In that last codepath, is there some obvious difference between “resizing” and “moving” the TopLevelDocument?