I'm also using the M1/M2/M3 as toggles for broadcasting modes.
With light actions, to show if a mode is on or off.
Key Broadcasting, Mouse Broadcasting and Keymaps...
If I leave the software running, I assume those would not be available for toggles any longer.
The device has programming whether the Logitech software is running or not. This is why when you boot up your system, before the Logitech software even runs, pressing buttons on a Logitech G-series keyboard will have default behaviors like pressing F1-F6.
If you want M1,M2,M3,MR programmed by the Logitech software, then leave the Logitech software running. If you want these buttons programmed by ISBoxer, then shut down the Logitech software.
This M-key behavior (change light states, reload different behaviors into the G-key banks) is built into the Logitech software, not the hardware. This is different from the typical G-key behavior (e.g. press key combo) which is mostly straight from the hardware. This is why shutting down the Logitech software prevents the M-key behaviors, but not the G-key behaviors, and why it is typically recommended to clear your profile and close the software, if you want to program the device through ISBoxer.
There are no conflicts between the two, and they can run in conjunction?
They
are running in conjunction whether you configure a conflict or not. Yes.
ISBoxer knows the physical state of the buttons on your Logitech device because the device provides this state information -- whether you program the device or not. Put another way: Any Hotkeys bound in ISBoxer to your Logitech device's buttons will fire, whether the button is programmed by the Logitech software (whether it is running or not) to do something else or not.
The only difference is if the button is programmed by the Logitech software to do something, it is going to do that too. So, if G600-G1 is configured in Logitech to send Mouse1, and G600-G1 it's configured in ISBoxer to send Mouse2, then when you press G600-G1, it's going to both press Mouse1 and Mouse2. ISBoxer does not prevent or override the Logitech-programmed behavior. If the button is not configured to do anything by the Logitech software, though, then nothing "extra" happens, there is no "conflict" and they "run in conjunction".
Clear as mud?
