Thanks for you comments. I personally have no use for this sort of thing, and honestly, I just cracked my skull over it for the challenge. So my next few comments are not in its defense.
With the form displayed, the document will not scroll as it seems it should using the mouse wheel. This is true even after adding a DoEvents statement.
I don't know every other interaction which may not seem right, but it seems to me that the purpose of the thing is to offer a "tip" and that there really shouldn't need to be any interaction until after the tip is displayed and dismissed?
Gerry, I couldn't replicate what you are seeing. But, I suspect it might be due to the call to the Show_HideTitleBar routine.
I discoved that I could eliminate the "wiggle" in the userform if the user wiggles the mouse in the control, if I reintroduced Jason's original bShowing test. However, in doing so when the form is displayed and I attempt to hide the title bar, the form displays with the font a little smaller and with a narrow white band at the bottom. If I add a DoEvents statement after the call to the Show_HideTitleBar routine, the form diplays normally (normal font size).
Reintroduction the bShow caused other problem. If I deliberately moved the cursor slowly (or what I would call normal speed) in and out of the control every thing seem normal. However, if I began to move the cursor (violently) in a circular motion around and in and out of the control, I began getting an RTE in the ShowForm procedure at the UserForm1.Left line of code.
Error handling seems to have prevented this.
I suppose that I am in full agreement with you Jason. It seems that we have created a rudimentary pseudo ActiveX control tool tip. If the occasional user understands its limitations then it may suffice, but I doubt that perfection is possible, or rather I know that it is with my limited abilities.
I've reattached the document with the changes discussed above.
Reply With Quote