Multimon area 52 code#

Nafxcwd.lib(wincore.obj) : warning LNK4006: _InitMultipleMonitorStubs already defined in winplace.obj second definition ignored Nafxcwd.lib(wincore.obj) : warning LNK4006: _g_pfnGetSystemMetrics already defined in winplace.obj second definition ignored Nafxcwd.lib(wincore.obj) : warning LNK4006: _g_pfnMonitorFromWindow already defined in winplace.obj second definition ignored Nafxcwd.lib(wincore.obj) : warning LNK4006: _g_pfnMonitorFromRect already defined in winplace.obj second definition ignored Nafxcwd.lib(wincore.obj) : warning LNK4006: _g_pfnMonitorFromPoint already defined in winplace.obj second definition ignored Nafxcwd.lib(wincore.obj) : warning LNK4006: _g_pfnGetMonitorInfo already defined in winplace.obj second definition ignored Nafxcwd.lib(wincore.obj) : warning LNK4006: _g_pfnEnumDisplayMonitors already defined in winplace.obj second definition ignored Nafxcwd.lib(wincore.obj) : warning LNK4006: _g_fMultiMonInitDone already defined in winplace.obj second definition ignored

Nafxcwd.lib(wincore.obj) : error LNK2005: already defined in winplace.obj Nafxcwd.lib(wincore.obj) : error LNK2005: _InitMultipleMonitorStubs already defined in winplace.obj Nafxcwd.lib(wincore.obj) : error LNK2005: _g_pfnGetSystemMetrics already defined in winplace.obj Nafxcwd.lib(wincore.obj) : error LNK2005: _g_pfnMonitorFromWindow already defined in winplace.obj Nafxcwd.lib(wincore.obj) : error LNK2005: _g_pfnMonitorFromRect already defined in winplace.obj Nafxcwd.lib(wincore.obj) : error LNK2005: _g_pfnMonitorFromPoint already defined in winplace.obj Nafxcwd.lib(wincore.obj) : error LNK2005: _g_pfnGetMonitorInfo already defined in winplace.obj Nafxcwd.lib(wincore.obj) : error LNK2005: _g_pfnEnumDisplayMonitors already defined in winplace.obj Nafxcwd.lib(wincore.obj) : error LNK2005: _g_fMultiMonInitDone already defined in winplace.obj Configuration: MUSHclient - Win32 Debug. Fixed to remove double-posting of a commit. However I note that, until you make a change, it now doesn't link for me (I commented on your commit on your branch).

In fact I had already committed your changes before I read this thread: This just involves work in writing, analyzing, testing, and checking. What I *am* resisting is some of the refactoring proposals where functions that currently work, are just being rewritten with a view to making them 'nicer'. So this must some other reality, the one where I ignore all suggested changes. I just don't recall 'never merging' any fixes he brought up. Nick Gammon Australia (22,777 posts) bio Forum AdministratorĪmended on Thu 12:39 AM (UTC) by Nick Gammon

So far, I put up a few branches on github in case any of you want to check out compatibility with VC++6, but it is all trivial thus far.

Multimon area 52 code#

I have zero intention of forking MUSHclient, and if anything 'new' that I code up can't be merged due to me fixing those warnings, it'd be a pretty useless endeavour, so I'd prefer to know before I spend too much time on such a project. Thus, my question to Nick is - are you willing to bring such fixes into your master, or did you have some sort of issues with it?

Since I hope to contribute, I'd like to pick up on that warnings-squashing project, since it is pretty much impossible to see the trees in the forest of warnings that even a partial build tends to throw up. But when I spoke to him it came up that Nick apparently never merged any of the fixes he brought up, and by now it would probably be a lost cause given the amount of new versions that have come out. I recall (what must by now be a pretty long time ago) that Twisol once started to fix up MUSHclient warnings in recent compilers.