Rick.Kazman@SEI.CMU.EDU (04/27/89)
I have implemented routines which allow me to move and resize child widgets by clicking on them with the mouse, emulating (sort of) the way that a window manager moves and resizes widgets. I did this by augmenting the translation tables with calls to my own routines, which in turn call XtResizeWidget and XtMoveWidget. However, it would look much better if I could get boundary boxes, the way that the window manager does. As it is now, you just click, move and click again, and the change gets made. Is there any way to do this in Xlib or Xt calls, or is this purely a window manager function? Thanks. rick
Rick.Kazman@CAD.CS.CMU.EDU (04/28/89)
I have implemented routines which allow me to move and resize child widgets by clicking on them with the mouse, emulating (sort of) the way that a window manager moves and resizes widgets. I did this by augmenting the translation tables with calls to my own routines, which in turn call XtResizeWidget and XtMoveWidget. However, n, and the change gets made. Is there any way to do this in Xlib or Xt calls, or is this purely a window manager function? Thanks. rick
kit@EXPO.LCS.MIT.EDU (Chris D. Peterson) (05/06/89)
> I have implemented routines which allow me to move and resize child widgets > by clicking on them with the mouse, emulating (sort of) the way that a > window manager moves and resizes widgets. I did this by augmenting the > translation tables with calls to my own routines, which in turn call > XtResizeWidget and XtMoveWidget. However, it would look much better if I > ncould get boundary boxes, the way that the window manager does. As it is > now, you just click, move and click again, and the change gets made. > Is there any way to do this in Xlib or Xt calls, or is this purely a window > manager function? There should be no problem with this, window managers are really just like any other X client. One possible approach to this is to select the window, unmap it, and then create a rubber_bank on a ButtonDown Event. Then move the rubberband on Button Motion, and finally place it on ButtonUp. You should have all the routines that you need to do this. Chris D. Peterson MIT X Consortium Net: kit@expo.lcs.mit.edu Phone: (617) 253 - 9608 Address: MIT - Room NE43-213