Use the New Window menu item to open up two or three new polygon windows.
Sets an event flag to tell the program to end.
#PUREBASIC OPENWINDOW WINDOWS#
If the map size reaches zero – there are no more open windows and DestroyPolygonWindow Here the child control references are removed from the map when a window is closed. Look at the DestroyPolygonWindow procedure. References are then used to resize the gadgets. This value is then used to retrieve child control references from the map and these Notice how the value of EventWindow is passed in from the event loop into this procedure. Look at the ResizePolygonWindow procedure. On the new window the references returned by these functions are stored in the map too. We then convert this to a string value and use this as When we create the window we capture the result of the OpenWindow() function in a Look at the CreatePolygonWindow procedure. POLYGONWINDOW structure previously defined. In the Variables section note that in addition to the usual variables to receive eventĭetails, a map called ActiveWindows is created using the Structure contains four integer values and so provides a place to store referencesįor a menu bar, a label, a combo box and an image plot. In the Structures section, note that the POLYGONWINDOW These will be shared on all the windows – although In the Enumerations section, note that there are only enumerations for the There are several things to notice about this program: A menu is provided to allow the creation of new windows or the closing of the A combo box is provided to allow a selection of polygons toīe drawn. This example program provides a window upon which a regular polygon is drawn in blue on aĬircumscribing grey circle. Increased flexibility that it can provide makes this well worth the effort. Organising this is a little more complex than the examples we’ve seen so far – but the Providing we keep track of all these references we can use this to our advantage. Generated and returned as a result of the function. When this constant is used as theĪrgument to the functions that support it, a unique reference number is automatically This is where the special #PB_Any constant comes in. Several files open at once or possibly to provide several different views of the same file. So what happens if a program needs to provide more than one copy of a window? Maybe to have This is fine in the simple programs we’ve demonstrated so far but presentsĪ problem in more complex programs – only one of each of these windows can exist at the To identify a single window and each gadget So far all of our examples have used a group of constants, an enumeration, Going to look into this a little further to find out why its so important. Or if you have experimented with the Form Designer tool, you may have noticed references to a Or for any of the gadget creation commands (for example ButtonGadget()) If you’ve looked at the help articles for the OpenWindow command It is therefore sometimes necessary to cancel the opening callback (UnbindEvent()) after opening the window or use flags.UserGuide - Dynamic numbering of windows and gadgets using #PB_Any The problem with this technique is that if you click several times on the same button, you still see only one window, but the system creates several iterations, so it becomes impossible to close the window. However, you can also mix the two techniques (classic and callback).īindGadgetEvent(#B2, - main event loop (alway one) Then you can also use CallBack (BindGadgetEvent()) but it's not necessarily simpler because this technique triggers the procedure at any time (so it can be re-triggered) which can complicate the task if procedures must be chained in an order. Either you group the events by window and then treat them by type, or you group them by type and separate them by window (not a very clear explanation, sorry) After that it depends on the number of events per window.
0 kommentar(er)
