Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Having multiple client instances breaks client-side message handling

#37

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.

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

State: open
Milestone: none
Assigned to: nobody

Activity

No comments yet.

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.