#37 open
Christopher Stawarz

Having multiple client instances breaks client-side message handling

Reported by Christopher Stawarz | July 13th, 2016 @ 11:40 AM

Every MWClientInstance has its own mw::Client instance. The latter's constructor invokes mw::initializeStandardVariables, which replaces any existing global variable objects with new ones. Since MWorks' global message functions (mprintf, merror, etc.) write to GlobalMessageVariable, all client-side messages generated via these functions are sent to the server to which the most recently created MWClientInstance is connected.

I'm not sure what the right solution is. Ideally, MWClient and its plugins simply wouldn't use the global message functions. However, given their ubiquity (particularly inside MWorksCore), that doesn't seem practical.

No comments found

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

MWorks Mac OS X/Cocoa Client Application

People watching this ticket