Okay, I can reproduce this pretty easily. The background:
I created a small object, based on advice from the sdc chat, that will show/hide my widgets when I mouse over it. Obviously, to do this, it has to stay visible. So I docked a thin white line to the right edge of my screen, 1 pixel wide, and set it to "Always on Top"... it has a mouseover script that simulates an "f10" press, which shows/hides all my widgets.
It functions correctly in that the object itself stays on the screen when widgets are hidden - as I expected it to do with "Always on Top" enabled. However, if there is a window that overlaps or reaches the edge of the screen, I noticed that the object would quit responding after a few uses. It turns out that although the object is staying visible, that when it simulates the f10 key to hide widgets, the object itself loses its z-order preference to be Always on Top. Clicking on the object brings it back to the top, but that defeats the purpose...
So the bug is, basically, that objects with "Always on Top" preference don't respond properly to an f10 "hide widgets" keypress. Either they are supposed to hide completely, which they don't (and I wouldn't think you'd want them to, because that's why you choose "always on top"), or they are supposed to stay fully visible, in which case the z-order needs to remain as it is supposed to be...
If I need to send a sample .dxpack of this object for testing, I can do that, but it should be pretty easy to reproduce this problem, as it is related to the interaction of "Always on Top" and F10 to hide/show widgets, rather than anything in this particular script itself...
