Search results

Create the page "Module" on this wiki! See also the search results found.

• Images
  ...ws it to open an image of various formats and display it. As the [[GFILE]] module is being used internally, the image can be stored on different sources such
  12 KB (1,905 words) - 15:38, 2 August 2021
• GTIMER
  µGFX comes with its own timer abstraction module. The GTIMER module provides high level, simple and hardware independent timers. Due to their n The API reference of the GTIMER module can be found [http://api.ugfx.org/group___g_t_i_m_e_r.html here].
  4 KB (598 words) - 15:51, 4 February 2016
• GEVENT
  The GEVENT module is a very powerful event system. It provides a way to create a '''many-to-m The API reference of the GEVENT module can be found [http://api.ugfx.io/group___g_e_v_e_n_t.html here].
  3 KB (442 words) - 15:00, 20 August 2021
• GEVENT FAQ
  ...wing is a small summarizing of frequently asked question around the GEVENT module. === What does the GEVENT module do? ===
  2 KB (362 words) - 01:29, 1 July 2014
• Getting Started
  ...d out the touchscreen. Everything is handled automatically in the [[GWIN]] module. The documentation of every module shows how to create these board files.<br/>See [[Board_File|board file]].
  6 KB (946 words) - 16:45, 29 July 2021
• Configuration
  ...the entire module. All the following sub-options only take effect when the module is enabled. |Enable or disable the entire GDISP module.<br/>See [[GDISP]].
  21 KB (3,115 words) - 17:53, 20 September 2017
• GWIN
  ...gets through a [[GINPUT#Touchscreen|touchscreen]]. However, the [[GINPUT]] module also allows to use other input methods as well. The API reference of the GWIN module can be found [http://api.ugfx.org/group___g_w_i_n.html here].
  5 KB (738 words) - 09:17, 16 April 2018
• Widgets
  ...able when a keyboard is used (either a physical one through the [[GINPUT]] module or a virtual on-screen one using the [[Keyboard|keyboard widget]]. A widget The GWIN module provides a simple implementation of widget styles. The widget style allows
  8 KB (1,170 words) - 11:19, 27 July 2016
• Progressbar
  ...omatically increased from its current to its maximum value. The [[GTIMER]] module is internally used for this purpose. No event is generated once the progres
  4 KB (517 words) - 15:48, 4 February 2016
• GFILE
  The GFILE module provides an operating system independent way of reading and writing files n The API reference of the GFILE module can be found [http://api.ugfx.org/group___g_f_i_l_e.html here].
  5 KB (879 words) - 10:15, 9 January 2017
• FATFS
  The GFILE module uses the well known [http://www.elm-chan.org/fsw/ff/00index_e.html elm-chan ...ed ''diskio.c'' which is pretty much like the board files of the [[GDISP]] module. It's purpose is to abstract the I/O interface to your disk.
  2 KB (346 words) - 19:47, 1 July 2014
• GOS
  ...[http://freertos.org FreeRTOS], or also just a bare metal system. The GOS module allows to write completely platform independent application code. The API reference of the GOS module can be found [http://api.ugfx.org/group___g_o_s.html here].
  14 KB (2,156 words) - 00:03, 24 September 2021
• GINPUT
  GINPUT is a powerful module which provides an easy way to interface different hardware peripherals such The API reference of the GINPUT module can be found [http://api.ugfx.io/group___g_i_n_p_u_t.html here].
  2 KB (280 words) - 18:53, 3 August 2021
• GDISP
  [[File:Gdisp_architecture.png|right|GDISP module architecture.]] The GDISP module provides a simple interface for graphic displays and a feature rich set of
  11 KB (1,675 words) - 15:50, 4 February 2016
• Architecture
  The library is split into different [[#modules|modules]]. Each module is responsible for a specific task such as [[GDISP|driving an LCD]], [[GINP '''Important:''' Each module has to be enabled in the [[Configuration|configuration file]] before it can
  3 KB (436 words) - 13:50, 4 March 2016
• Multiple displays
  It's possible to drive more than just one display out of the [[GDISP]] module. Each display is completely independent. The displays can have different di
  6 KB (905 words) - 17:19, 19 May 2016
• Remote displays
  The [[GDISP]] module offers the possibility to connect a remote display. ...ory floor. A technican can now go to the device and just hook up a display module and he'll have the same view as the operator on the remote display. This ca
  4 KB (740 words) - 13:10, 1 July 2016
• Drawing
  The [[GDISP]] module offers many high-level API calls to draw single pixels, [[#Primitives|primi ...utines provided by the GDISP module are also available within the [[GWIN]] module. Drawing will then occur relative to the windows position.
  6 KB (911 words) - 19:41, 11 December 2016
• Board File
  Certain [[Architecture#Module|modules]] have to communicate to hardware in order to fulfil their tasks. T
  1 KB (180 words) - 19:27, 19 December 2016
• GAUDIO
  ...UDIO module provides high level API for handling audio in- and output. The module provides built-in decoders but does also allow to use external codecs. See The API reference of the GAUDIO module can be found [http://api.ugfx.org/group___g_a_u_d_i_o.html here].
  5 KB (833 words) - 15:50, 4 February 2016
• GQUEUE
  The API reference of the GQUEUE module can be found [http://api.ugfx.org/group___g_q_u_e_u_e.html here]. ...m an SD-Card using the [[GFILE]] module and output it using the [[GAUDIO]] module.
  2 KB (387 words) - 15:51, 4 February 2016
• Touchscreen Calibration
  ...devices such as touchscreens needs to be calibrated. For this, the GINPUT module provides a calibration dialog. The calibration uses a three-point algorithm ...ult the calibration dialog will pop-up on every power-up unless the GINPUT module could load valid calibration data. See [[Touchscreen_Calibration#Storing ca
  6 KB (950 words) - 14:15, 24 May 2017
• TextEdit
  ...ither be a physical keyboard (or keypad) interfaced through the [[GINPUT]] module or the virtual on-scree [[Keyboard|keyboard widget]].
  643 bytes (103 words) - 15:49, 4 February 2016
• GTRANS
  ...an application can be changed dynamically during runtime using the GTRANS module. The API reference of the GTRANS module can be found [http://api.ugfx.io/group___g_t_r_a_n_s.html here].
  6 KB (748 words) - 17:25, 23 August 2021
• Creating a widget
  ...can therefore represent 32 flags. Some of these flags are used by the GWIN module internally to store certain information like the enable state, the visibili The VMT is defined by the GWIN module. The custom widget simply creates an instance of that struct and fills in t
  17 KB (2,421 words) - 10:09, 9 September 2021
• Using PSoC Creator
  * ILI9341 display module with SPI interface In our example project we are using an ILI9341 display module connected over SPI. For this, we need to add an SPI component to the PSoC p
  6 KB (910 words) - 00:43, 18 August 2016
• Using Eclipse
  Now in the ''gfxconf.h'' file enable the corresponding GFX module to start using the driver. In this case the ''#GFX_USE_GDISP'' has to be se
  13 KB (2,283 words) - 14:03, 28 May 2017
• Changes from V2.x to V3.0
  While all board files will need to be rewritten, the new GBUS module will make that process much simpler. Most board interface files will now be == The New GBUS Module ==
  9 KB (1,449 words) - 12:25, 10 March 2018