I’m using the “inside” channel of a panel to zero out or let pass keyboard keys that should only be active within a given panel.
I find it a bit more friendly than “focusselect” because it’s on only if the mouse is in that panel, no clicking to activate/deactivate a panel focus involved.
Unfortunately, I’ve noticed that even though I run consistently above 30 fps (I know 60 is the ideal, but I don’t think we have many 3D apps running a 60 right now), often times I will move the mouse outside of the panel and the inside channel will still be on! It depends how fast I move it and where I move it.
the specific instance of the inside channel staying on is when I have a textport partially over it. If I move - fast, because if I do it slow it works - from the panel onto the textport that’s over the panel, then inside will stay on. Once I’m on the textport, I can move anywhere - even change apps - and the inside channel will always stay on.
which of course causes all kinds of unpleasant behavior when I type in Touch and my app thinks I’m typing keys inside the panel (one of the things that happen is that when I type in the textport I don’t see the keys I trap with the keyboard…)