Printable View
Hey.
im making my own front end, but i have a Q. for other developers of front-end.
the way im about to do it, is (by the way its C#) i got a form, and in that form, i use usercontrols to be used as menu's.
how do others do it..
ex code, og just explanations would be great.. thanks :nw: :nw: :nw:
if you can understand VB6, download the Road Runner Source and have a look at that.
Can you make a quick paint image of what you are trying to do? Why are you using user controls as menus? There is a built in menu control. It is in the System.Windows.Forms name space.Quote:
Originally Posted by Mcnovy
He's probably wanting to create an interface that is skinnable and uses graphics for the buttons. There are a few ways to do this. Is this what you are trying to accomplish?
Ineffigy
yes.. that is exactly what i am trying to :)
do any of you have an prober way to do it..?
www.codeproject.com ? :)
You might want to look into "Owner Drawn" controls. This allows you to have control over how the controls (buttons, drop down menus , etc) are created. Another idea is to generate your own controls using DirectX. This will allow for hardware acceleration and alpha blending techniques. It all depends on how fancy you want to get.
a simple way would be to work on an image, and have a file that defines clickable areas. To begin with, you can have one image. then you can start adding images that are hidden, and the button you press, reveals that part of the hidden image and so giving the illusion of animation.
this would be a much better way than to use a form. however, for rapid develipment (and you can worry about skinning later) you can use a form, but make sure you dont' embedd too much into the actual buttons, and just have the buttons calls methods. in that way, when you do implement the code for a skin, you can point the click-over to the method.
hope that helps
Why not go a step further and have an XML file that defines each object, the properties (aka images) of the object and the method to be called from being "clicked" on or any other event. This way the screen becomes totally customizable and you can work on the background processing instead of focusing on the interface.
that's exactly what I said :)