🚀 go-pugleaf

"vERUs" <-verus-@telia.com> wrote in message
news:3f95ac40@newsgroups.borland.com...

> The 'x' is there alright... the declaration is in the "multimon.h"
> header file.

Yup, the following statement:

    #define MonitorFromPoint    xMonitorFromPoint

will be a problem.  The typical solutions probably apply - #undef
MonitorFromPoint in your own code prior to including Forms.hpp (which is
where TScreen is declared), or else alter the order of header includes so
that Forms.hpp is included before multimon.h so that the declaration does
not get messed up.

> It says something about a COMPILE_MULTIMON_STUBS
> declaration but I don't know if that has anything to do with it.

No, it does not, because the offending #define is declared outside of the
COMPILE_MULTIMON_STUBS block.

> I'm starting to think it might be easier to just get the
> ProcAddress and dynamically link the function myself.

TScreen::MonitorFromPoint() already uses the multimon.h MonitorFromPoint()
function.  But it also does a little more, since it then has to translate
the returned HMONITOR to a TMonitor for the VCL's use.  If you call
Multimon::MonitorFromPoint() directly, then you'll have to do that
conversion manually.


Gambit