Tab binding for a showTip toplevel

[sl1200mk2]

Hi,
in my app I have a showTip display by a button with -per10 0, so it stays visible as long as you don't click on it.

would it be possible for such tip to be destroyed on binding? or if not destroyed to respond on binding and let the focus goes to the next toplevel?

best regards,
Nicolas

[aplsimple]

Hi Nicolas,

Firstly, I'd recommend using -eternal 1 instead of -per10 0, because -eternal 1 doesn't disable other tips while -per10 0 does. Though, if you are going to disable other tips, use -per10 0 😀

Secondly, if you want to destroy (hide) a tip by force, use hide function this way:

::baltip hide $w yes

where $w is the widget path of the tip.

E.g. if your tip relates to the root "." then use:

::baltip hide . yes

Best wishes,
Alex

[sl1200mk2]

Hi Alex,
thank you for the -eternal 1 tip

Secondly, if you want to destroy (hide) a tip by force, use hide function this way:

that was not what I'm asking :)
in Tk there's binding for

event add <<PrevWindow>> <Shift-Tab>
event add <<NextWindow>> <Tab>

but Tips do block those bindings.
Do you think I need to handle them in my app or it's something baltip can handle?

++
Nicolas

[aplsimple]

I'm not sure, but it looks like your WM gives the focus to the tip's toplevel so that no response from Tab/Shift -Tab. I'm using Windows and Linux (Xfce, Gnome, Mate, Fluxbox). I didn't ever notice this quirk. Thanks for the informing.

I'll try to add -focus option to baltip's tip (to showTip and showBalloon as sequence), meaning the widget path that should be given the focus after the tip window becomes visible. In your case, it's the clicked button that has to be focused.

I.e. the call would be something like:

::baltip tip . "Button .but was clicked" -eternal 1 -alpha .8 -fg white -bg black -geometry +99999+100 -bell 1 -focus .but

The baltip repo will be updated tomorrow.

[sl1200mk2]

Hi Alex,
I've tried your latest code (with -focus) but it does not work here... moreover it would be great if such an option does not exists and <Tab> binding allow to set the focus to the next toplevel in stackOrder, not the one I define.

if you want I can test :)

best regards,
nicolas

[aplsimple]

Hi Nicolas,

Would you be kind to compose and present me a minimum code snippet illustrating the issue?

Because, obviously, we understand it differently.