2
I Use This!
Activity Not Available

News

Analyzed about 3 years ago. based on code collected almost 4 years ago.
Posted about 13 years ago by SEWilson
syncing default BlockedKeys with the string in my registry
Posted about 13 years ago by SEWilson
moving "blocked keys" out of the registry, also re-implementing defaults based on my current preferences (e.g. "Q" for MBXTARGET and "E" for MBXFOLLOW), playing WoW and don't like Escape or Tab to multicast, etc.
Posted about 13 years ago by SEWilson
removing Control.Registry class
Posted about 13 years ago by SEWilson
removing old regsitry read/write calls
Posted about 13 years ago by SEWilson
relocating IsCaptureEnabled and refactoring the IsRepeatKey() check so that it still updates "pressedKeys" correctly
Posted about 13 years ago by SEWilson
adding option to disable "IsRepeatKey" filtering, it's an experimental option not exposed in the UI
Posted about 13 years ago by SEWilson
Users need the ability to configure "local only" keys, e.g. keys which are not captured by Mubox, and immediately re-post for the OS to handle.Comments: ** Comment from web user: SEWilson ** In the latest dev build, you can run Mubox once to generate ... [More] a .config file, then edit it to add global hotkeys. There is currently no UI, here is the structure. Your config section will look different: <MuboxConfig> <Keys> <add InputKey="LeftWindows" OutputKey="LeftWindows" SendToDesktop="true" /> </Keys></MuboxConfig>The above allows the Windows Key to process, and causes Mubox to short-circuit (do no processing) for the key. You can replace "LeftWindows" with the key of your choice such as "F" or "R". You could even re-map "LeftWindows" to the hotkey you use for Ventrillo, including any of the Control-Alt-Shift Modifiers. [Less]
Posted about 13 years ago by SEWilson
adding new KeySettingCollection to MuboxConfig, to be used in conjunction with the new "SendToDesktop" key setting to short-circuit the keyboard input hook and let the OS process the key normally (intended to fix a problem with hotkeys for Ventrillo, etc.)
Posted about 13 years ago by SEWilson
CAS is short for "Control-Alt-Shift", also known as modifier keys, thus "CAS Modifiers" in Mubox terminology.The "Server" Computer will manage "Key Settings" per Client, the configuration is managed with an app.config section. There is no UI for ... [More] editing CAS Modifiers (yet)When the Server captures Keyboard Input...1) If there is no Key Setting for a pressed key, current behavior applies.2) If there is a Key Setting, both the VK and CAS Modifiers for the key pressed are modified according to the Key Settings before being processed further by Mubox.3) If the Key Setting specifies EnableNoModActiveClient=True, then the "Active Client" does not have CAS Modifiers applied.This will allow several things:"dead keys" - causing slaves to process a keypress such as "V" when the user presses "K", where "V" is not bound to anything, but allowing the "active client" or "master" to process the key normally"mubox hotkey swaps" - swapping mubox hotkeys with other keys if the mubox hotkey is "in your way", such as NUM LOCK for AutoRun"FTL" macros - applying a different modifier key combination to each group member for in-combat "/target" changingThis does not solve the problem of allowing hotkeys through for other applications such as vent, but adds the necessary support.This new behavior functions independently of Keyboard Multicast.Key Settings only apply on the SERVER MACHINE. editing them on a client machine will have no effect on the clients.Comments: ** Comment from web user: SEWilson ** My 'Q' button used to be bound to the MBXTARGET macro. The problem with MBXTARGET is that it relies on "Macro Rewriting" based on leader changes. This doesn't work when in-combat, creating an achilles heal in PvP.I now have my 'Q' button bound to a macro named "CAS" which looks like this:/target [nomod,target=target][mod:ctrl,mod:shift,target=Shon-target][mod:ctrl,mod:alt,target=Crysauce-target][mod:alt,mod:shift,target=Paperface-target][mod:ctrl,mod:alt,mod:shift,target=Helenaya-target][mod:ctrl,target=Ziiggee-target]This relies on the following Mubox Config, which defines each of my clients (via the UI) and each client's Key settings (via hand editing, search for "OutputModifiers"):<?xml version="1.0" encoding="utf-8"?><configuration> <configSections> <section name="MuboxConfig" type="Mubox.Configuration.MuboxConfigSection, Mubox, Version=1.4.0.0, Culture=neutral, PublicKeyToken=null" /> </configSections> <MuboxConfig mouseCloneMode="Pressed" preferredTheme="Default" autoStartServer="true" EnableMulticast="true" autoRunOnQuickLaunch="true"> <Clients> <add Name="SHON" CanLaunch="true" EnableIsolation="true" MemoryMB="1280" ServerName="localhost" ServerPortNumber="17520" PerformConnectOnLoad="false" ApplicationPath="D:\WoW\wow.exe" IsolationPath="D:\MBX\" ProcessorAffinity="0" WindowPosition="0,0" WindowSize="0,0" InstallWoWAddOn="true" WindowHandle="0"> <Keys> <add InputKey="Q" OutputKey="Q" OutputModifiers="CONTROL, SHIFT" EnableNoModActiveClient="true" /> </Keys> </add> <add Name="CRYSAUCE" CanLaunch="true" EnableIsolation="true" MemoryMB="1024" ServerName="localhost" ServerPortNumber="17520" PerformConnectOnLoad="false" ApplicationPath="D:\WoW\wow.exe" IsolationPath="D:\MBX\" ProcessorAffinity="0" WindowPosition="0,0" WindowSize="0,0" InstallWoWAddOn="true" WindowHandle="0"> <Keys> <add InputKey="Q" OutputKey="Q" OutputModifiers="CONTROL, ALT" EnableNoModActiveClient="true" /> </Keys> </add> <add Name="PAPERFACE" CanLaunch="true" EnableIsolation="true" MemoryMB="1024" ServerName="localhost" ServerPortNumber="17520" PerformConnectOnLoad="false" ApplicationPath="D:\WoW\wow.exe" IsolationPath="D:\MBX\" ProcessorAffinity="0" WindowPosition="0,0" WindowSize="0,0" InstallWoWAddOn="true" WindowHandle="0"> <Keys> <add InputKey="Q" OutputKey="Q" OutputModifiers="ALT, SHIFT" EnableNoModActiveClient="true" /> </Keys> </add> <add Name="HELENAYA" CanLaunch="true" EnableIsolation="true" MemoryMB="1024" ServerName="localhost" ServerPortNumber="17520" PerformConnectOnLoad="false" ApplicationPath="D:\WoW\wow.exe" IsolationPath="D:\MBX\" ProcessorAffinity="0" WindowPosition="0,0" WindowSize="0,0" InstallWoWAddOn="true" WindowHandle="0"> <Keys> <add InputKey="Q" OutputKey="Q" OutputModifiers="CONTROL, ALT, SHIFT" EnableNoModActiveClient="true" /> </Keys> </add> <add Name="ZIIGGEE" CanLaunch="true" EnableIsolation="true" MemoryMB="1024" ServerName="localhost" ServerPortNumber="17520" PerformConnectOnLoad="false" ApplicationPath="D:\WoW\wow.exe" IsolationPath="D:\MBX\" ProcessorAffinity="0" WindowPosition="0,0" WindowSize="0,0" InstallWoWAddOn="true" WindowHandle="0"> <Keys> <add InputKey="Q" OutputKey="Q" OutputModifiers="CONTROL" EnableNoModActiveClient="true" /> </Keys> </add> </Clients> </MuboxConfig></configuration> [Less]
Posted about 13 years ago by SEWilson
interdependent refactors - tested stable retiring Control.Registry adding Mubox.Configuration namespace, this will replace all Registry-backed configuration currently in place adding "CAS Modifiers" support, no UI yet but tested functional by ... [More] hand-editing the config file, breaks keyboard compatibility with pre-1.4 clients another bug-fix to the "Game Isolation" feature, this version of the code now correctly creates the root directory for isolation (i distinctly recal this being fixed already.) "themes" are now read from disk (you can edit them!) if requested I'll allow for data templates of clients, and templating of the item surface panel (for custom switcher look-and-feel) [Less]