Path: utzoo!attcan!uunet!cs.utexas.edu!asuvax!ncar!boulder!stan!ninja!toml From: toml@ninja.Solbourne.COM (Tom LaStrange) Newsgroups: comp.windows.x Subject: Re: pushpins in OL (was: OSF statements about OPEN LOOK) Message-ID: <1990Sep19.140334.20042@Solbourne.COM> Date: 19 Sep 90 14:03:34 GMT References: <1990Sep13.204215.5215@Solbourne.COM> <1990Sep14.172922.27088@alphalpha.com> <142694@sun.Eng.Sun.COM> Sender: news@Solbourne.COM Reply-To: toml@solbourne.com Organization: Solbourne Computer, Inc. Lines: 34 In article <142694@sun.Eng.Sun.COM>, argv@turnpike.Eng.Sun.COM (Dan Heller) writes: |> I argued before that all good window managers (motif, open look, twm) |> should provide some method for dismissing all toplevel windows -- if |> you are not using one that does, this could be considered pilot error. |> I have been convinced that this isn't really a strong argument. Thus, |> I think the best solution is for the XView toolkit to provide its own |> pushpin item and not require the window manager to provide it automatically. Are we coming full circle back to the X10 days when if a client wanted a titlebar it created one for itself? We went through this very problem when developing the Open Look side of the OI toolkit. Our dialog boxes started out with their own pushpins and titles, not relying on the window manager to provide them. Then we ran across this OLCI document thing that told us how to ask the window manager for pushpins and other stuff. So we changed our dialog boxes to use this interface and let the window manager provide the pushpin and title. One problem we ran into was the pushpins on popup menus. When the menu begins life, it is an override-redirect window and therefore the window manager doesn't see it. Because of this, the pushpin in the menu has to be owned and operated by the menu. When the user pins it, should the pushpin still be part of the menu or provided by the window manager? Well, we chose to keep it as part of the menu so the user could unpin it when not being used with an Open Look compliant window manager. Of course one can only hope that our menu pushpins look and act exactly like the pushpins provided by the window manager so as not to confuse the user... -- Tom LaStrange Solbourne Computer Inc. ARPA: toml@Solbourne.COM 1900 Pike Rd. UUCP: ...!{boulder,sun}!stan!toml Longmont, CO 80501