![]() Tests if monitors in a multi-monitor setup are using the same display colour format. Launch Explorer, Find Files, and the Run Dialog, open the Start Menu, Minimize all windows, and launch Windows Help, all using three lines of code and the keybd_event API. GetSystemMetrics: Determine Windows Start-up ModeĪPI to determine if Windows is currently running in Normal Mode, Safe Mode, or Safe Mode with Network Support. How to determine the current screen docking position(s) of taskbars, and their state (on-top, hidden etc.). SHAppBarMessage: Determine TaskBar Position Using SystemParametersInfo to return the co-ordinates of the screen not covered by taskbars. SystemParametersInfo: Determine Available Screen Real Estate Turn power saving-enabled monitors off/on. But, the creation routine of the requester has problems to place the requester properly.SendMessage: Change the Display Power State So the toplevel handling works as expected. Moreover, the requester afterwards move with the position of the secondary monitor. Which means displayed outside the visible area in case the primary monitor is the bottom one. The requester in BWidget is always displayed below the primary monitor. I would prefer the first one (Better or additional I would like to have requester displayed relative to the mouse for faster working). The other is to display the requester always at the primary monitor. One is to display the requester at the same monitor as the main window. This behaviour is as expected.īut the requester is displayed not as expected! Other application have two strategies to dispaly requester/dialog boxes. What we see is that the main toplevel windows will stay in place and the coordinates are changing depending of the position of the secondary monitor. Jnc What about this proc, does it not answer the question "Do I have dual monitors?" I am unsure, though, on some linux desktops that may have virtual sizes set. This is the same two monitors - just using a different version of Tk. Just to really make things crazy, when I run the proc on Windows XP directly, using Tk 8.4.10, I get a 1 returned from DualMonitors, with $sw = 1024 and $mw = 2308. When I run the Solaris Tcl/Tk (8.5a6) from Sun, what I see is DualMonitors returning a 0, $sw having a value of 2304, and mw having a value of 2289. Another thing I have is that the two monitors run at different resolutions. they display one extra wide desktop, where I can drag X or Windows apps from one scren to the other. Oh, and I have the dual monitors running in "Cinematic" mode - i.e. I have dual monitors, controled by Windows XP and then, via Exceed, running Sun GNOME on a SPARC. LV DualMonitors doesn't work for me either. If we can find some way to identify the coordinate range too, then I know a Tk bug we can close :) This can be important for trying to decide if a window or menu is going to fall off the edge of the viewable area (done in BWidgets and Tk). If I set the leftmost monitor as primary, then my range would be 0 - 2304. Here windows may be placed from -1152 to +1152. Which is corrent for this setup, but doesn't say anything about the possible coordinate range. So my system which has the secondary monitor to the left of the primary yields: BWidgets and parts of Tk have been modified to accomodate this, but this is the first time I have seen an example of how to get the available workspace size within Tk. Thus is a valid geometry string (note the +-). This has the interesting effect of setting a monitor to the left or above to have negative coordinates. This helps applications that try to center windows to actually center them in a monitor and not split them over two monitors. PT: The standard Windows multiple screen setup extends your desktop over N monitors but depending upon where you get your information from, the desktop size is returned as the size of the primary monitor whose top left coordinate is set as 0,0. only reports the width of the primary monitor. For my setup, the value for sw is 2624 (1600 + 1024) and the value of mw is (curiously) 2609.ĭKF: Hmm. I've got dual monitors but the proc returns 0. This doesn't work when running wish on MacOSX with X11. See get_display_* Changes in CVS, not yet in an official release (aimed at 2.0) - 9Mar07 And there is now a high level Tcl interface as well. RT quick news flash: twapi now supports the bare Windows api needed for multi-monitor work according to the author.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |