I didnt very much understand what you are looking at.
But if you want to add picture to your command button:
cmdOkay.Picture = "Images\Pict.bmp"
If you want some image control to act like a button then you can add code to the MouseDown event to change the image and make it look like a button. Or you can use 2 overlaying images.
Or probably under samples check Create "coolbar" control effects.
do (_samples+"\solution\solution.app" && To run the samples
i want create shaped button with any shape, for example triangular button, circle button ecc
the button, get 5 parameter
-image
-image on muose over
-image on clik
-image on disable
-image mask (black and white) or trasparent color
for example if i want circular button, i give at the button this property:
-image: image with orange circle and white background
-mouseover: image with red cirle and white bg
-click: img with blu circle and white bg
-disable: img with gray circle and white bg
-mask: black circle in white bg or transparent color=white
now, in my form i have a circular orange button.
but button work only if i click inside the circle.
i think, for create this control must use a region.
and with this contol we are able to create button with any form.
i want create shaped button with any shape, for example triangular button, circle button ecc
You can make circles with the shape control and change the curvature to 99. But being a beginner as you get experience you will find that the most important part and more difficult part to learn in VFP is the code that will be executed when you click that button. There are classes on the internet that will help you acheive what you want, as suggested by ShyFox go to
A couple of suggestions before you decide whether these "fancy" controls. Here an article that describes the general rules in User interface guidelines.
You may find that for a developer creating buttons of all shapes is chalenging and interesting but for a user consistency and Look-and-feel for "standard components" is more what they need.
Mike Gagnon
If you want to get the best response to a question, please check out FAQ184-2483 first.
Just to endorse the advice given by Mike, there are 2 main criteria in developing a VFP application
It must work and it must be intuititive.
If your application is not intuititive, you will be costing your client money through the additional time a user needs to become familiar with the interface you have provided.
That is a short road to nowhere, and could be extremely damaging to your career as a developer.
It can also bring the reputation of VFP into disrepute which is something that all of us here are anxious to avoid.
So, I suggest you join the 'boring' ones amongst us and concentrate on developing applications that enhance the reputation of VFP rather than risk damaging both your reputation and that of VFP.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.