I do not plan to make any changes to your original source, just simply incorporate it into Tin圜AD’s fabric. There are also other developers out there (mostly in non-English speaking countries) that get copies of the source as soon as I release it and then they re-release it in other languages (still under the LGPL license). Tin圜AD gets between 100 and 200 downloads per day, so once I release the bug fix that will incorporate your Multimon classes, it will be next to impossible to stop its distribution. I am not aware of any conflicts, but at the very least, out of courtesy, thought that I should inquire whether you are aware of any licensing conflicts that would prevent me from using your unchanged source in a GNU LGPL open source project?
#Multimon api for free
I am managing an open source project called Tin圜AD, an electrical schematic capture program available on I have run into some problems in Tin圜AD where it needs to know about multiple monitors and am planning to use your MFC wrapper classes to implement some bug fixes.ġ) Have you made any newer changes to MultiMon since you made the source available on Code Project, or any other classes or enhancements that I should know about before incorporating it into Tin圜AD? Are there any limitations that you know of when used on Windows XP (any service pack) in conjunction with Microsoft Visual Studio 2003/2005/2008? I doubt that there are, but am just trying to be careful.Ģ) Tin圜AD is licensed for free using the GNU LGPL license. I find that it is still relevant and useful today. Thanks for writing the Code Project article on multi-monitor classes in February of 2003. - Made changes to make compatible with VC6 environment.This has proved to be a safe assumption empirically but isn't necessarily a guarantee. Known LimitationsĬMonitor and CMonitors rely on the assumption that a monitor handle does not change. I haven't really gone too far with this class but it seemed like a logical part of the library. determines if the specified item on the monitorīOOL IsOnMonitor( const POINT pt ) const īOOL IsOnMonitor( const CWnd* pWnd ) const īOOL IsOnMonitor( const LPRECT lprc ) const ĬMonitorDC is a CDC derived class that represents a monitor specific device context. Void GetWorkAreaRect( LPRECT lprc ) const the work area is the monitor rect minus the start bar Void GetMonitorRect( LPRECT lprc ) const creates a device context for the monitor - the client is responsible for DeleteDC Void CenterWindowToMonitor( CWnd* const pWnd,
Using the CodeĬMointor is a basic MFC class that allows you to safely use the multi-monitor API on any Win32 platform.ĬMonitors represents the collection of monitors currently attached to the system and wraps the EnumDisplayMonitors API function.Ĭonst BOOL UseWorkAreaRect = FALSE ) const The multi monitor classes take care of including multimon.h correctly depending on the value of WINVER. These wrappers interrogate the runtime OS and either make fall-through calls into the actual API or return the properties of the one (and only) monitor on those older platforms. Multimon.h also provides some stub functions that allow calls to be safely made on Windows 95/NT4 machines. If you #define WINVER to be greater than 0x400, you don't need to link to multimon.h, as the API gets defined in windef.h for Windows 98 and later targeted builds. It has some new constants to pass to GetSystemMetrics and a couple methods to enumerate all of the monitors currently attached to the system and get the properties of a given monitor.Īll of the types and functions are defined by the platform SDK in the file multimon.h. The API itself is simple and straightforward. BackgroundĮverything you ever wanted to know about the API for multiple monitors is described in a very well written article by David Campbell in the June 1997 issue of MSJ. On those platforms, they just provide the properties of the one and only monitor. These classes can be safely used on Windows 95/NT4 as well. This project is a couple of small MFC classes that wrap the multi-monitor API. Well, the first thing he noted was a glaring bug: he uses multiple monitors and my screen saver only showed up on one.Īfter some scouring of the internet and research into MSDN, I was able to get the screensaver running on multiple monitors by using some API calls that were introduced with Windows 98/2000. After I got my first implementation up and running, I shipped it off to a friend. A while ago, I decided to write a screensaver application as a way to pick up MFC.
0 kommentar(er)
