T.R | Title | User | Personal Name | Date | Lines |
---|
2590.1 | Is this a Bug or a Feature? | STU01::BGEISELHART | | Wed Apr 25 1990 07:41 | 20 |
| Hello again,
no help anywhere???
May be I have not said clearly what my problem is, please excuse
my bad english.
I have an application with a lot of windows. When I resize a window
with the resize button in the upper direction everything is fine.
But now the windowmanager should now (configure request) that not
just width and height have changed, but also x and y. He should,
but he don't. When I now try to reset the Window with Xtsetvalues
to old x and y and maybe old width and height, windowmanger changes
width and height but leaves x and y the same, maybe because he has
not recognized that they where changed by the resize button.
Is this a known bug, are there work arounds, when will it be fixed,
...????
Starting holiday on 3rd of May, but this must be fixed before.
Thanks Bianca.
|
2590.2 | Some ideas... | LEOVAX::TREGGIARI | | Thu Apr 26 1990 09:34 | 26 |
| > But now the windowmanager should now (configure request) that not
> just width and height have changed, but also x and y. He should,
> but he don't.
I don't remember the exact details of what goes on here, but it is
complicated by the fact that your application's shell widget is
*really* a child of a window manager window and *not* the root
window. That is, your window's *real* x and y are
(-border_width, -border_width) if I remember correctly, since our
window manager displays its own borders. I think there should be
a 2nd "synthetic" configure_notify event (generated by the window
manager) that will come along and tell you the new x and y. It's
"synthetic" because as far as the server is concerned, the x and
y of your window have *not* changed.
> When I now try to reset the Window with Xtsetvalues
> to old x and y and maybe old width and height, windowmanger changes
> width and height but leaves x and y the same, maybe because he has
> not recognized that they where changed by the resize button.
You may be running into a timing problem if you are reacting
directly to the first configure_notify. But as I said, I don't
remember the exact details...
Leo
|
2590.3 | Known (to some, at least) | DECWIN::KLEIN | | Mon Apr 30 1990 13:47 | 9 |
| > Is this a known bug, are there work arounds, when will it be fixed,
> ...????
Yes, I believe it is a "known bug". I've run into it, too. No idea whether
it will (ever) be fixed.
I haven't found a workaround, but I haven't worked on it too hard, either.
-steve-
|