By exposing the Button, TextBox and Label, you could make changes to them - with a bit of designer hodge-podge, and a few PropertyGrid attributes you might be able to get that code into the Designer.cs files, where it would normally be. If the controls are exposed, you can hook the events as usual. It would probably be immensely boring to add the controls manually, but IMO it'd look better than one humongous switch statement. You could also try putting the name of the Button which should be clicked in the Tag property of the TextBox and having a common KeyPress handler for every TextBox which reads the Tag, searches for a Button with that name in the Parent's Controls collection, and clicks it
Between the idea
And the reality
Between the motion
And the act
Falls the Shadow
By exposing the Button, TextBox and Label, you could make changes to them - with a bit of designer hodge-podge, and a few PropertyGrid attributes you might be able to get that code into the Designer.cs files, where it would normally be.
Wouldn't that require a new control for each group box? It might be worth it in the future, but for now I'll stick to the multiple button solution.
If the post was helpful, please vote!
Book: Devils by Fyodor Dostoyevsky
Project: Hospital Automation, final stage
Learning: Image analysis, LINQ
Noone is going to just hand over the entire source code for such a large project.
It is not as easy as you think it is. You need intimiate knowledge of how Windows works, how the Shell works, plug-in support in your own application, writing and exposing an API that thes plugins would use to interface with your SideBar, ..., yada, yada, yada...
You need not use cmd.exe as it the command shell which would automatically get invoked.
your executable file here is /C" + "\"\"C:\\Program Files\\ThinTV\\PLINK.EXE and your arguments is appliance@%ThinConnectedFrom%" + " " + "-pw appliance" + " " + "\"killall -q vlc; export DISPLAY=.0; vlc --halfscreen --key-vol-up 100 rtsp://stfamtv0001/streama\"\""