Mubox (Legacy)

[workitem:2738]The idea is that you shouldn't "lose" mouse events while switching between clients.1. Confirm that Mouse Capture is functional during ALT-TAB (client switch)2. Implement Mouse Button Click events "correctly": Sending a "Click ... [More] Instruction" (MouseDown+MouseUp) when the user Completes a "Click" (MouseUp Event from User) instead of sending the MouseDown and MouseUp event separately as the User sends them.3. Implement "Mouse Drag" events "correctly": A "Drag" begins if the user holds a mouse button down for more than 250ms. "MouseDown" is sent when a Drag begins, and the client message identifies it as a drag (as opposed to a "Click").4. If a Drag is outstanding and the user begins Activation of another client, the Drag must be "closed" (MouseUp), the Drag then re-opens on the "Activated" client. [Less]

I would like to have the option of disabling the mouse capturing altogether. Right now i run 2 clients on 1 machine, and all the system does with its mouse capturing is give me a headache.Its mildly buggy in a way i can't describe well, but one point ... [More] is when i try to click the icon on the task bar, i have to drag the window out from under it, just to click any of the the items under it.If the 2 windows overlap even a tiny bit, i can't properly click into one of them. even with alt tabbing, it still retards up the mouse events and is really annoying.ATM ive just downloaded the source and commended out most of the mouse code, which solved my issues [Less]

Currently, [Mouse Clone] requires that your client windows overlap to properly broadcast the mouse to multiple clients. Unfortunately users who have multiple displays aren't able to make use of Mouse Clone. It currently only really works well for ... [More] users who..(1) Have a Single Computer, and have their Game Windows the same size and position (overlapping) or..(2) Have Multiple Computers, running one client per computer (or, multiple clients per computer conforming to point (1) above) [Less]

pre-1.4 refactor - multiple changes to input handling code, and identifier names related to state management to clarify intent, Known Issues: as stable as 1.3.0.69, however, this and all prior versions have a problem with losing mouse capture to ... [More] their target window, you may notice the cursor graphic "glitching" when using mouse clone. also, mouse clone is still constrained to overlapped windows of matching dimensions (though, "maximized, windowed mode" can give most players a full-screen effect and this is a non-issue for mouse cloning between multiple computers each running a single game client [Less]

correcting storage of window position+size so it only occurs when the option has been enabled

fixing problem with app not shutting down correctly

I'm wanting to implement "FTL". This is how I intend to implement it within Mubox.Total CAS (Control-Alt-Shift) States = 2^3 = 8 Group Members (including "active client")To keep things simple, these will be automatically assigned as Mubox Clients ... [More] need them. A Mubox Client's "CAS Modifiers" will be displayed in the Mubox Server UI next to the Client IP Address. These "CAS Modifiers" identify the client as a specific target, during Multicast the CAS Modifiers for the "Active Client" are used as part of the broadcast to all clients. Thus, all clients know which client is "Active".1. Commands will be added to Muboxer which allow you to change the "CAS Modifiers" for each Group Member. These will be persisted to saved vars and shared among all group members for auto-generation of "MBXCAS" macro.2. A new macro ("MBXCAS") will be generated using "CAS Modifiers" to determine how to /target in-combat. This macro can be added as an Action Button for /click and key-binding access, depending on your 'FTL-style'.3. A new "Keyboard Configuration" UI is necessary that lets us "opt-in" certain keys for "CAS Modified" behavior. These are the only keys that will be sent with CAS Modifiers. [Less]

[workitem:2738]Comments: Resolved with changeset 32326.

adding new option "Disable Mouse Capture", also re-worked the "Mouse Clone" menu options so that they are more natural feeling.

[workitem:2738]The idea is that you shouldn't "lose" mouse events just because you are switching between active clients, though this does nothing to correct the existing problem, it would be a more consistent behavior that can be worked with later.