DONE: On Screen Button That Sends Keyboard Commands

[Ath]

Is it possible to make the buttons transparent? The idea would be to create all the graphics for the buttons in one large single background image - all carefully arranged, of course, so that the positions matched the transparent buttons above.

-nudone (October 11, 2011, 03:51 PM)

I've been experimenting with that a few weeks back,

-Ath (October 11, 2011, 05:08 PM)

Did some more experiments (and been busy with work-stuff, so it took some time), but reversed it all, because all I could get working was a set of nearly invisible buttons, with no graphics on it. I think I'll leave the transparent stuff out for now, unless it is very important to anyone.
I have other things on the list that are imho more useful, like a multi-state button, and combining button-groups into 1 layout, that would like some attention, but time is still a bit limited ATM.

[cranioscopical]

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

-Ath (October 24, 2011, 03:31 PM)

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

[nudone]

Sounds good to me. Groups could be an interesting feature if you can move the buttons around as a group; could be a way to speed up the design of button layouts.

(I'm still waiting for the new pc to arrive.)

[nudone]

I've made a post here about why I'm not using the MIMO touchscreen anymore: https://www.donation....msg270234#msg270234

[Ath]

After a year of silence in the development department of WinButtons, now there is another release for both WinButtons and WinButtonEdit.

A Coding Snack request by ConstanceJill in this thread prompted me to suggest WinButtons as a solution, but it was missing the feature of parameter entry.
That is now solved
And WinButtonEdit is also updated to support these new features of WinButtons.

Some screenshots are added to the release message.

Here's an update release of:

WinButtons 3.6.0.0

and

WinButtonEdit 1.1.0.0

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.

A ToDo for a QuickEdit feature is noted but not available yet, that'll be the next thing I'll work on.

Any feedback or feature requests are still welcome, as usual

[cranioscopical]

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.
 

[nudone]

I'm glad to see that you are still working on WinButtons, Ath. One day I'll start using it again - just need a compatible PC setup that works with the horrible touchscreens (that assume you are using a single monitor setup).

[Ath]

that assume you are using a single monitor setup

-nudone (October 10, 2012, 07:19 AM)

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

-nudone (October 10, 2012, 07:19 AM)

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

[Ath]

Some bugs where swatted out of the new showParams feature of WinButtons and WinButtonEdit.

So here's an update release of:

WinButtons 3.6.0.2

and

WinButtonEdit 1.1.0.2

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

[Ath]

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:

WinButtons 3.6.1.0

and

WinButtonEdit 1.1.0.3

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

[cranioscopical]

Nice