Okay, Juce is upgraded, but the problem remains. The advice about HIViewComponentPeer was excellent, here’s what I found:
In [ void Component::setAlwaysOnTop (const bool shouldStayOnTop) ] I end up in this code:
if (! peer->setAlwaysOnTop (shouldStayOnTop))
// some kinds of peer can’t change their always-on-top status, so
// for these, we’ll need to create a new window
const int oldFlags = peer->getStyleFlags();
Appearently, this “kind of peer” does not cause problems on PC. In general, what kinds of peers cause problems like this? What is the easiest way to convince the peer to be another “kind of peer” that won’t cause problems?
Another thing I noticed, is that pretty much ALL the time an HIViewComponentPeer is created, the variable ‘viewToAttachTo’ is NULL. Now, since my problem is that a subcomponent “falls through” the view it is supposed to (remain) attach(ed) to - maybe the error is that ‘viewToAttachTo’ is not the view I wish it to be? It should be obvious that I’m not at all sure what ‘view’ refers to, what a peer really is, or what is generally going on, so I hope there are some similar problems out there, or a hunch to go by…
Thanks in advance!