| | [ Return to Bugs & Features | Roadmap 1.1 | SVN ⇄ GIT ]
STR #781
| Application: | FLTK Library |
|---|
| Status: | 1 - Closed w/Resolution |
|---|
| Priority: | 3 - Moderate, e.g. unable to compile the software |
|---|
| Scope: | 2 - Specific to an operating system |
|---|
| Subsystem: | Core Library |
|---|
| Summary: | FLTK Applications do not work properly on secondary display (Windows specific) |
|---|
| Version: | 1.1.6 |
|---|
| Created By: | tommie |
|---|
| Assigned To: | mike |
|---|
| Fix Version: | 1.1-current (SVN: v4227) |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
No files
Trouble Report Comments:
| |
| #1 | tommie
08:41 Mar 30, 2005 |
| When running an FLTK Application on the secondary display of a dual monitor setup, the following problems occur:
* Submenus are not positioned right (they appear on the left side of the parent menu, as if there is 'no space' on the right).
* popup windows (e.g. tooltips, context menus, etc.) popup on the wrong monitor (they popup on the primary monitor).
The 'menubar' demo gives a good overview of things that go wrong. Note that this is all specific to Windows. | |
| |
| #2 | mike
12:41 Mar 31, 2005 |
|
| |
| |
| #3 | mike
12:43 Mar 31, 2005 |
| Fixed in Subversion repository.
OK, this is now fixed in Subversion and will be part of tomorrow's weekly snapshot. Please confirm so we can close this one out...
Summary: added Fl::screen_count() and Fl::screen_xywh() APIs to handle multiple monitors properly.
| |
| |
| #4 | tommie
03:55 Apr 01, 2005 |
| Works like a charm! And my complements for the amazing speed at which this issue got resolved: very well done!
Only sidenote is that people may need to update their Windows SDK to support the API calls used (I did), so you may receive some trouble reports there...
| |
| |
| #5 | mike
06:24 Apr 01, 2005 |
|
Hmm, EnumDisplayMonitors is listed as Win98 and higher, what compiler are you using?
| |
| |
| #6 | tommie
06:36 Apr 01, 2005 |
| I'm using Visual C++ 6.0 with SP6 on Windows XP with SP2. Also, adding a "#define WINVER 0x0500" would also do the trick, but this would would generate the following compiler message:
NOTE: WINVER has been defined as 0x0500 or greater which enables Windows NT 5.0 and Windows 98 features. When these headers were released, Windows NT 5.0 beta 1 and Windows 98 beta 2.1 were the current versions. For this release when WINVER is defined as 0x0500 or greater, you can only build beta or test applications. To build a retail application, set WINVER to 0x0400 or visit http://www.microsoft.com/msdn/sdk to see if retail Windows NT 5.0 or Windows 98 headers are available. See the SDK release notes for more information.
| |
| |
| #7 | mike
15:38 Apr 10, 2005 |
|
Matthias's latest changes should take care of that... | |
[ Return to Bugs & Features ]
|
| |
