![]() The directory structure could look like that: įor example, to build a program which handle two windows, we will have to create two form files and one main file. Every form file should be named with the '.pbf' extension, so it will be correctly opened by the IDE. The event procedures needs to be defined somewhere in the source code. An event procedure can be assigned to every gadget, and will be handled automatically in the event loop. It can not have two form in the file (in other words, it should never have two in the same file). ![]() The form designer has been created to allow modular forms and easy maintenance. Using the form designer in real world projects When a gadget is selected on the form, its properties are display on this panel and can be modified here. Select one, and draw directly on the form the size needed. The image and its path can be changed easily here. ![]() A form is built from code, so if a change is made directly in code view, it will be reflected visually.ĭisplay all the images currently used by the form. It will bring automatically the form panel tool on top.Ĭhange the form view, switch from design mode to code view. The code parser isn't the same used by the compiler and therefore doesn't support all features, so when doing manual changes to a form file, it has to remain basic.Ĭreate a new empty form. A form file is a regular PureBasic file, so it can be easily modified without even open the form designer. It supports almost all native PureBasic, and even. The PureBasic IDE has a very powerful integrated form designer, which allows to design easily windows and arrange gadgets on them.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |