[comp.windows.open-look] OL Pushpin

kkirksey@eng.auburn.edu (Kenneth B. Kirksey) (05/17/91)

I'm currently writing an application using OLIT 2.5 and the Open Look Widgets,
and I'm a little confused over the Pushpin resource.  What I want to happen
is that every time I open a popup with a pushpin I want the pushpin to be
in.  So, in the callback to pop up the pop up, I set the pushpin resource
for that popup to OL_IN before I pop it up.  No Luck. When I close the pop
up with the pushpin and open it back up, the pin is still out.  I looked
in the OLIT manual and it seemed to say that you could only set the 
INITIAL state of the pin, which made no sense.  Has anyone else had
this problem?  Does any one know of a way to accomplish what I want to do
here?

+---------------------------+------------------------------------------------+
| Ken Kirksey               | "Any government that robs Peter to pay Paul    |
| Computer Engineering      |  can always count on the support of Paul"	     |
| Auburn University         |                                                |
| kkirksey@eng.auburn.edu   |                        -Robert A. Heinlein     |
+---------------------------+------------------------------------------------+

toml@marvin.Solbourne.COM (Tom LaStrange) (05/21/91)

|> I'm currently writing an application using OLIT 2.5 and the Open Look Widgets,
|> and I'm a little confused over the Pushpin resource.  What I want to happen
|> is that every time I open a popup with a pushpin I want the pushpin to be
|> in.  So, in the callback to pop up the pop up, I set the pushpin resource
|> for that popup to OL_IN before I pop it up.  No Luck. When I close the pop
|> up with the pushpin and open it back up, the pin is still out.  I looked
|> in the OLIT manual and it seemed to say that you could only set the 
|> INITIAL state of the pin, which made no sense.  Has anyone else had
|> this problem?  Does any one know of a way to accomplish what I want to do
|> here?

You need to set the pin_initial_state member of the _OL_WIN_ATTR property to
_OL_PIN_IN.

--
(I kid you not)Tom LaStrange        toml@Solbourne.COM

mls@cbnewsm.att.com (mike.siemon) (05/28/91)

> I'm currently writing an application using OLIT 2.5 and the Open Look Widgets,
> and I'm a little confused over the Pushpin resource.  What I want to happen
> is that every time I open a popup with a pushpin I want the pushpin to be
> in.  So, in the callback to pop up the pop up, I set the pushpin resource
> for that popup to OL_IN before I pop it up.  No Luck. When I close the pop
> up with the pushpin and open it back up, the pin is still out.  I looked
> in the OLIT manual and it seemed to say that you could only set the 
> INITIAL state of the pin, which made no sense.

This works fine with the USL OPEN LOOK window manager and the
OPEN LOOK 4.0 toolkit (the code Sun used to produce OLIT 2.5).
The set_values method in the OPEN LOOK VendorShell properly
checks for a change in the XtNpushpin resource and notifies
the window manager. I've not checked the OLIT 2.5 source to
see if this was changed, but I will.

The (USL) reference manual correctly states that the XtNpushpin
resource is settable, in the section describing Shell resources.
It incorrectly states the resource cannot be set, in the
PopupWindowShell man-page. I don't have the OLIT 2.5 rewrite
of these pages to check.

Note that the window manager gets involved here. That's why I
pointed out which window manager I tested this with. I assume
the person quoted above is using the OpenWindows window manager.
It is pure conjecture on my part to suggest the OpenWindows
window manager may be blocking (or ignoring) the pushpin
state change, but it is something to investigate.

Steve Humphrey
UNIX System Laboratories