anton@postgres.uucp (Jeff Anton) (07/28/88)
Given the increasing close date of X11R3 being let out I'm wondering about resize hint changes. Specfically, we have min, max, and increment now; but that's not enough information to have a window manager report window sizes for resize actions for many applications. Right now, maybe this is a widely know bug, xterm will loose its window increment properties if the scroll bar is added. What should happen in this case? I think that an extra hint of min increment needs to be added. So if you had a text window with a vertical scrollbar with a minimum dimension of the text region of 10x6, the hints would be as follows: inc x fontwidth inc y fontheight min x 2 * internalborder + widthscrollbar + 10 * fontwidth min y 2 * internalborder + 6 * fontheight min x inc 10 min y inc 6 With this information, a window manager can report the correct number of text lines durring a resize operation, and applications can put graphic widgets such as scrollbars on windows without causeing problems for the window manager. Or I could be completely mistaken, Jeff Anton
dshr@SUN.COM (David Rosenthal) (07/28/88)
Read the Inter-Client Conventions Manual that was sent out with R2, section on WM_NORMAL_HINTS. David.
ellis@AUDI.SIEMENS.COM (Ellis Cohen) (07/28/88)
> Given the increasing close date of X11R3 being let out I'm wondering > about resize hint changes. Specfically, we have min, max, and increment > now; but that's not enough information to have a window manager report > window sizes for resize actions for many applications. Right now, maybe > this is a widely know bug, xterm will loose its window increment > properties if the scroll bar is added. What should happen in this case? > I think that an extra hint of min increment needs to be added. base_width and base_height have been added to WM_NORMAL_HINTS for just this purpose. You can read about them in the draft of the Inter-Client Communications Manual that was included on the R2 tape. Ellis Cohen