T.R | Title | User | Personal Name | Date | Lines |
---|
1209.1 | Intrinsics Shell bug | LEOVAX::TREGGIARI | | Tue Aug 01 1989 09:15 | 15 |
| There is a problem in the Intrinsics shell code. When the shell
is first realized, and when the shell is resized at the request
of its child, it sets the hints property but doesn't bother to
check to see if the min/max size hints need to be set.
Since you are going around the Intrinsics, it wouldn't know
anyhow. What you can do for now (DECwindows V1 AND V2; i.e.
it's not fixed in V2...) is do an XtSetValues of XtNminWidth
and XtNminHeight on the shell AFTER it is realized.
You will need to do the XtSetValues again if your widget hierarchy
ever requests a change in the shell size.
Leo
|
1209.2 | It works but I get a warning. | EPIK::J_JOSEPH | Have you seen Jack in the Green | Tue Aug 01 1989 12:07 | 6 |
| Your suggestion did work. Thanks. But, when I set the min width and height,
I get a warning saying "X Toolkit Warning: Window Manager is confused".
Do you know how I can avoid getting this message?
-Jonathan
|
1209.3 | | LEOVAX::TREGGIARI | | Tue Aug 01 1989 13:42 | 9 |
| > I get a warning saying "X Toolkit Warning: Window Manager is confused".
> Do you know how I can avoid getting this message?
I don't know what causes that, but I know you won't get it with
DECwindows V2 (because the message was taken out). I personally don't
know any way around it in V1.
Leo
|
1209.4 | Still there | COMICS::CARLETON | Roundabout Basingstoke way | Wed Aug 02 1989 07:28 | 11 |
|
> I don't know what causes that, but I know you won't get it with
> DECwindows V2 (because the message was taken out).
I beg to differ but I get this message when running more than 3-4
Xterms together on a VS2000 (ULT3.0 UWS2.0).
Les
|
1209.5 | Who devised that naming scheme? | CASEE::LACROIX | Object oriented dog food? No, sorry | Wed Aug 02 1989 11:18 | 12 |
| Re .4:
> > I don't know what causes that, but I know you won't get it with
> > DECwindows V2 (because the message was taken out).
>
> I beg to differ but I get this message when running more than 3-4
> Xterms together on a VS2000 (ULT3.0 UWS2.0).
UWS2.0 is definetely a "DECwindows V1" environment.
Denis.
|
1209.6 | V1, V2? | COMICS::CARLETON | Roundabout Basingstoke way | Thu Aug 03 1989 13:47 | 8 |
|
Apologies,
Which version of UWS does DECwindows V1+ appear in?
Les
|
1209.7 | need more help | EPIK::J_JOSEPH | Living in the Pasture | Tue Oct 24 1989 15:20 | 23 |
| I got things working fine for my main window. This is the code segment which
worked for defining the min and max width and height for resizing the main
window.
Arg al[5];
XtSetArg (al[0], XtNminWidth, main_min_wd);
XtSetArg (al[1], XtNminHeight, main_min_ht);
XtSetArg (al[2], XtNmaxWidth, screen_wd);
XtSetArg (al[3], XtNmaxHeight, screen_ht);
XtSetValues (toplevel, al, 4);
Recently I tried to do the same thing for a popup dialog box which I created.
I used the same method, but I replaced "toplevel" with the popup dialog box
widget id. It didn't work.
Does anyone know how I can define the min and max width and height for the
resizing of a popup dialog box?
Thanks.
-Jonathan
|
1209.8 | You need to set them on a shell widget | GR8FUL::HERBERT | Orwell was only off by a few years | Tue Oct 24 1989 15:55 | 14 |
| Instead of using the widget ID of the popup widget, you have two choices:
1. Use XtParent(popup) - the toolkit creates a hidden shell widget behind your
back - this is the widget you need to set the attributes for.
2. Use XtCreatePopupShell to create a shell widget yourself, and then create
a dialog box (non-popup) as a child of the shell widget. Set the attributes
on the shell widget.
I recommend method #2, as it doesn't make any assumptions about the internal
nature of the toolkit.
Kevin
|