From be68bd465e0df039e823113acf8c69779306037a Mon Sep 17 00:00:00 2001 From: "donal.k.fellows@manchester.ac.uk" Date: Thu, 5 Jul 2012 09:49:40 +0000 Subject: [Bug 3538401]: Better description of the key difference between [wm geometry] and [winfo geometry] --- ChangeLog | 6 ++++++ doc/wm.n | 8 ++++++++ 2 files changed, 14 insertions(+) diff --git a/ChangeLog b/ChangeLog index 7a7b56d..c74f093 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,9 @@ +2012-07-05 Donal K. Fellows + + * doc/wm.n (geometry): [Bug 3538401]: Better description of the key + difference between [wm geometry] and [winfo geometry]; the former + represents the window manager's understanding, not Tk's. + 2012-07-04 Donal K. Fellows * win/tkWinDialog.c (GetFileNameW): [Bug 3540127]: Clean up the tables diff --git a/doc/wm.n b/doc/wm.n index f234b6d..59aa624 100644 --- a/doc/wm.n +++ b/doc/wm.n @@ -227,6 +227,14 @@ If \fInewGeometry\fR is specified as an empty string then any existing user-specified geometry for \fIwindow\fR is cancelled, and the window will revert to the size requested internally by its widgets. +Note that this is related to \fBwinfo geometry\fR, but not the same. That can +only query the geometry, and always reflects Tk's current understanding of the +actual size and location of \fIwindow\fR, whereas \fBwm geometry\fR allows +both setting and querying of the \fIwindow manager\fR's understanding of the +size and location of the window. This can vary significantly, for example to +reflect the addition of decorative elements to \fIwindow\fR such as title +bars, and window managers are not required to precisely follow the requests +made through this command. .TP \fBwm grid \fIwindow\fR ?\fIbaseWidth baseHeight widthInc heightInc\fR? This command indicates that \fIwindow\fR is to be managed as a -- cgit v0.12