a multi-state button, and combining button-groups into 1 layout

Sounds good to me FWTW. I can see the appeal of transparent buttons but I'd rather not see progress mired by one feature.

I've made a post here about why I'm not using the MIMO touchscreen anymore: http://www.donationcoder.com/forum/index.php?topic=27865.msg270234#msg270234

Looking forward to trying it.

Using your earlier work and a MIMO screen (and Nudone's input on the topic) I was able to create quite a useful setup for a friend of mine with very bad arthritis. Part of his business involves video editing: being able to touch buttons instead of chasing menus with a mouse and/or hot keys with a keyboard afforded him considerable relief.

that assume you are using a single monitor setup

I'm still using the dual-monitor (from a single video card, NVidia GeForce GTS 250) setup I've been using ever you so generously sent me the MIMO. I updated to the latest DisplayLink drivers, a few weeks ago (and also a few months ago, with the previous major update). The initial flashing during/after boot is still there, but it works as expected, and flawlessly fwiw.
I recall your issues are caused by the dual-videocard setup, that isn't properly understood by the DisplayLink drivers, as they are in fact an alternative to a multi-videocard setup.
There are even a few standard-size monitors (22"/27", Full HD) that are just USB connected (and using DisplayLink technology).(Philips, Samsung), but these aren't in the league you require for your graphics work

I'm glad to see that you are still working on WinButtons

This was triggered by a feature request/coding snack, but it was fun to be pounding on the code again, after a year of silence (though I did a lot of other type & languages programming in the meantime)
I've been trying, a few times already, to re-do WinButtons in .NET/WPF, just to get acquainted with WPF, but I've not found the motivation to complete that yet, and there are a lot of bears on the road. Some things that are easy function-calls in AutoIt3, are quite daunting tasks in plain .NET C# code

WinButtons just learned a new trick: Drop a .ini or .wbuc file (with a valid WinButtons config inside) on it and it'll open that configuration, if no On Drop command is defined for the button you dropped it on. (Also accepts if dropped on the background or on an input control)
Some bugs where ironed out of WinButtonEdit.

Another update release of:
and

Download available from the release message, linking to my DCMembers pages.

Updates can be downloaded also from the WinButtonEdit File/Check for updates option, using DCUpdater when installed.

Any feedback or feature requests are still welcome, as usual

Okay, I'm still liking the capabilities of WinButton over the iPad, Keypad Pro. The important feature being program aware context switching layouts.

I have to ask, though, has anyone had WinButtons working on a mini touchscreen, such as a MIMO or a Lilliput device.

The main problem I foresee is that when pressing the touchscreen to activate WinButton, it will cause the mouse cursor to jump to the touchscreen button location - where it will then stay and require moving back with the mouse - which isn't really what is desired when using a touchscreen. (Sorry, if this problem has already been resolved and I've just not been keeping oup with the thread.)

Okay, I'm still liking the capabilities of WinButton over the iPad, Keypad Pro. The important feature being program aware context switching layouts.

I have to ask, though, has anyone had WinButtons working on a mini touchscreen, such as a MIMO or a Lilliput device.

The main problem I foresee is that when pressing the touchscreen to activate WinButton, it will cause the mouse cursor to jump to the touchscreen button location - where it will then stay and require moving back with the mouse - which isn't really what is desired when using a touchscreen. (Sorry, if this problem has already been resolved and I've just not been keeping oup with the thread.)