All we know controls cant be overlaped in Xojo. So, to create some functionality, some controls have to be created in another window. In my case, a little window, with no other controls and the interface drawn in the paint event.
All works great, but, it needs a ToolTip, but the window clas has no HelpTag property
The xojo way, Use the ToolTip Class, No problem, MouseEnter -> Show and it closes automatically BUT wait, it colses in 1 second, no way someone is going to read it in that time, ok, that part its broken, lets try with autoHide = False, and a MouseExit -> Hide. It wworks but, what is that, not a ToolTip, just a plain ugly yellow window. no animation, no the system color, no way to blend in with the rest of the interface.
Is any other way to add a native ToolTip to a window?
Is the ToolTip clas NOT native in MacOS and Linux?
What are you doing to make the tooltip disappear after a second? Have never seen this.
I have been using attached windows (MAAttachedWindowMBS) for the last years. The main problem was that the MouseExit event didnât always fire. Show an attached window, change to another app, move the mouse there and when you go by to the Xojo app the MouseExit never fires.
Therefore, Iâm going back to a status area help.
In the call of ToolTip.Show Just leave the default value autoHide = True. The tool tip disapears in about 1 or 2 seconds, It is useles, there is no way to set a autoHide behavior with more time.
[quote=420273:@Beatrix Willius]Now Iâm confused. What are you doing? There is no Tooltip for 64bit macOS:
ToolTips do not appear on 64-bit macOS builds.[/quote]
That depends on your Xojo version. Early 64-bit ones worked if you reversed the sign on the y axis value. In essence, the y = 0 was the bottom of the screen instead of the top. That got fixed later, and now y must be given as a positive offset. I donât recall exactly when it was fixed. IIRC, up to 2017R3 you used a negative y for 64 bit macOS builds.
If you need to share a common class or module across Xojo versions, you can use #If statements to decide when to reverse the y axis value.
[quote=438528:@Dave S]Is this something that was âfixedâ, and the LangRef wasnât updated?
or what?[/quote]
Yes, but I donât recall which version had the fix. And before that, someone discovered the Y offset was negative instead of positive so in the broken versions you could still make it work by reversing the sign on the Y coordinate. Or thatâs how I recall it anyway. Itâs in the forums somewhereâŠ
