Frame - Revision history

Tectu: /* Example */

2016-08-11T19:01:22Z

‎Example

Tectu: /* Buttons */

2016-02-10T10:20:11Z

‎Buttons

Tectu: /* Buttons */

2016-02-10T10:19:17Z

‎Buttons

Tectu: /* API reference */

2016-02-04T15:50:04Z

‎API reference

Tectu: /* API reference */

2015-02-14T00:16:27Z

‎API reference

Inmarket: /* Example */

2014-08-16T14:19:37Z

‎Example

Inmarket at 14:18, 16 August 2014

2014-08-16T14:18:19Z

Tectu at 09:04, 7 August 2014

2014-08-07T09:04:12Z

Tectu at 21:03, 1 July 2014

2014-07-01T21:03:37Z

Tectu at 18:37, 1 July 2014

2014-07-01T18:37:43Z

@@ Line 163: / Line 163: @@
          switch(pe->type) {
              case GEVENT_GWIN_SLIDER:
-                 if (((GEventGWinSlider *)pe)->slider == ghSliderR || \
+                 if (((GEventGWinSlider *)pe)->gwin == ghSliderR || \
                                                          ghSliderG || \
                                                          ghSliderB ) {
@@ Line 171: / Line 171: @@
              case GEVENT_GWIN_BUTTON:
-                 if (((GEventGWinButton *)pe)->button == ghButton1) {
+                 if (((GEventGWinButton *)pe)->gwin == ghButton1) {
                      gwinSliderSetPosition(ghSliderR, rand() % 256);
-                 } else if (((GEventGWinButton *)pe)->button == ghButton2) {
+                 } else if (((GEventGWinButton *)pe)->gwin == ghButton2) {
                      gwinSliderSetPosition(ghSliderG, rand() % 256);
-                 } else if (((GEventGWinButton *)pe)->button == ghButton3) {
+                 } else if (((GEventGWinButton *)pe)->gwin == ghButton3) {
                      gwinSliderSetPosition(ghSliderB, rand() % 256);
+                 }

@@ Line 24: / Line 24: @@
 == Buttons ==
-The frame widget can optionally implement a close button. It shows up as an 'x' in the top right hand corner. If the button is pressed, <code>gwinDestroy()</code> is automatically called on the frame widget. Therefore, the entire widget including all its children will be destroyed. However, in certain cases it might be useful not to destroy the frame widget as this also destroys all children and therefore might take a long time to recreate which can lead to performance issues when the frame widget is often used. To prevent the frame widget of being destroyed upon clicking the close button, the flag <code>GWIN_FRAME_KEEPONCLOSE</code> can be passed to the <code>gwinFrameCreate()</code> function. If that flag was specified, the frame widget will not be automatically destroyed when the close button is clicked. Note that with this flag specified, the close button does not hide the frame - the user application will still need to trap the ''CLOSE'' event and manually set the frame to invisible using <code>gwinHide()</code>. The flag just prevents the frame window from being automatically destroyed when the close button is pressed.
+The frame widget can optionally implement a close button. It shows up as an 'x' in the top right hand corner. If the button is pressed, <code>gwinDestroy()</code> is automatically called on the frame widget. Therefore, the entire widget including all its children will be destroyed. However, in certain cases it might be useful not to destroy the frame widget (and all its children) but just hiding it instead. To prevent the frame widget of being destroyed upon clicking the close button, the flag <code>GWIN_FRAME_KEEPONCLOSE</code> can be passed to the <code>gwinFrameCreate()</code> function. If that flag was specified, the frame widget will not be automatically destroyed when the close button is clicked. Note that with this flag specified, the close button does not hide the frame - the user application will still need to trap the ''CLOSE'' event and manually set the frame to invisible using <code>gwinHide()</code>. The flag just prevents the frame window from being automatically destroyed when the close button is pressed.
 The close button can be enabled by passing <code>GWIN_FRAME_CLOSE_BTN</code> as a flag to the <code>gwinFrameCreate()</code> routine.

@@ Line 24: / Line 24: @@
 == Buttons ==
-The frame widget can optionally implement a close button. It shows up as an 'x' in the top right hand corner. If the button is pressed, <code>gwinDestroy()</code> is automatically called on the frame widget. Therefore, the entire widget including all its children will be destroyed.
+The frame widget can optionally implement a close button. It shows up as an 'x' in the top right hand corner. If the button is pressed, <code>gwinDestroy()</code> is automatically called on the frame widget. Therefore, the entire widget including all its children will be destroyed. However, in certain cases it might be useful not to destroy the frame widget as this also destroys all children and therefore might take a long time to recreate which can lead to performance issues when the frame widget is often used. To prevent the frame widget of being destroyed upon clicking the close button, the flag <code>GWIN_FRAME_KEEPONCLOSE</code> can be passed to the <code>gwinFrameCreate()</code> function. If that flag was specified, the frame widget will not be automatically destroyed when the close button is clicked. Note that with this flag specified, the close button does not hide the frame - the user application will still need to trap the ''CLOSE'' event and manually set the frame to invisible using <code>gwinHide()</code>. The flag just prevents the frame window from being automatically destroyed when the close button is pressed.
 The close button can be enabled by passing <code>GWIN_FRAME_CLOSE_BTN</code> as a flag to the <code>gwinFrameCreate()</code> routine.

@@ Line 2: / Line 2: @@
 == API reference ==
-The API reference for the basic container can be found [http://api.ugfx.org/master/group___frame.html here].
+The API reference for the basic container can be found [http://api.ugfx.org/group___frame.html here].
 == Custom Draw Routines ==

@@ Line 2: / Line 2: @@
 == API reference ==
-The API reference for the basic container can be found [http://ugfx.org/images/resources/doxygen/master/group___frame.html here].
+The API reference for the basic container can be found [http://api.ugfx.org/master/group___frame.html here].
 == Custom Draw Routines ==

@@ Line 64: / Line 64: @@
      wi.g.x = 10;
      wi.text = "Colorpicker";
-     ghFrame1 = gwinFrameCreate(0, &wi, GWIN_FRAME_BORDER | GWIN_FRAME_CLOSE_BTN | GWIN_FRAME_MINMAX_BTN);
+     ghFrame1 = gwinFrameCreate(0, &wi, GWIN_FRAME_CLOSE_BTN | GWIN_FRAME_MINMAX_BTN);
      // Apply the button parameters

@@ Line 1: / Line 1: @@
 [[File:Frame_example_1.PNG|right|frame|Color picker example using the frame widget.]]The frame widget is based on the [[container]]. It behaves like a window similar to the ones you know from your computer. It has a border, a window title and an optional button to close it.
 == Window title ==
@@ Line 8: / Line 27: @@
 The close button can be enabled by passing <code>GWIN_FRAME_CLOSE_BTN</code> as a flag to the <code>gwinFrameCreate()</code> routine.
 == Example ==

← Older revision		Revision as of 09:04, 7 August 2014
Line 8:		Line 8:

	The close button can be enabled by passing <code>GWIN_FRAME_CLOSE_BTN</code> as a flag to the <code>gwinFrameCreate()</code> routine.		The close button can be enabled by passing <code>GWIN_FRAME_CLOSE_BTN</code> as a flag to the <code>gwinFrameCreate()</code> routine.
−
−	~~== Overlay ==~~
−	If you want to use the frame widget as some kind of message box, then you have to note the following: The window manager of uGFX does currently not handle transparent inputs. This means that widgets that are "below" the frame are still being triggered when the area "above" them is being touched. To workaround this issue, a root container can be created that fills the entire screen size. Every widget and container will be added as a child to this root container. Hide the root container before the frame widgets shows up using <code>gwinHide()</code> and make it visible again using <code>gwinShow()</code> once the frame has been closed.

	== API reference ==		== API reference ==