This page was started on Saturday, July 13, 2002.

[Rohan Pall] writes about his short but lively experience with tk_popup:

'''Why do I care about this?'''

My '''ultrat''' (ultra table) package makes it easy for me to quickly make auto-scrolled tables that have a cool way of hiliting the item under the mouse.  I also wanted a popup when the right-button is clicked over an item, like you've prolly seen in lots of progs.  The problem was that tk_popup is inconsistent on different platforms.  So I worked around it.  Now I'm showing you what I figured out in the hopes that it helps y'all.    And this way I'll remember a year from now what I was doing ;)

'''Platform diffs'''

I've noticed some diffs with tk_popup on windows and on unix, specifically on Windows98 and on Linux.  I use $::tcl_platform(platform) to test what platform I'm on, i.e. "windows" or "unix".

'''windows''':
   * The <Unmap> binding isn't fired when the popup dissapears, which includes when the user doesn't select one of the menu items.
   * All processing of the script stops as soon as the popup is displayed.  The script continues where it left off after the popup dissapears.

I'm assuming this happens because the native windows menu widget is being called, and not a Tk toplevel.  All I know for sure is that I have observed this widget phenomena.  Here is an

'''unix''':
   * Here the <Unmap> binding actually gets fired when the popup dissapears.
   * Processing of the script continues after the popup is shown.  The rest of the script doesn't wait for the popup to dissapear.

This inconsistent behavior causes problems when doing cool things with The Cool Language.