![]() ![]() See this recent article with members of freedesktop regarding their views of the direction desktop applications and libraries are headed ĭKF: xprop? To understand that, you need to understand that every X window has a set of mappings called properties associated with it. Interesting related reading: an emerging window manager specification that extends ICCCM. arswm (at one time available from Bill Burdick via email).You use Tk's wm command to interact with the window manager. Nor should there be anything that the app can do about it the user should be in control after all. Typically, applications communicate with window managers by providing them with hints they can ask to be a certain size and at a certain position, but ultimately if the WM decides to put the window somewhere else (e.g., because the user moved or resized it) then there's nothing that the app can do about it. (You should only see a significant difference when something crashes, and that shouldn't happen in the first place!) ![]() On Windows and Macintoshes, that responsibility is divided up slightly differently internally, but the net result is usually the same. This application is called the window manager. In the X Windowing System, there is (usually we exclude situations like web kiosks here) a single special application whose responsibility is to look after the arrangement of windows (e.g., allowing people to drag them around and resize them) and the look and feel of the decorations of the window (title bar, frame, etc.). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |