Skip to content

v0.11.0

Compare
Choose a tag to compare
@ImpulseAdventure ImpulseAdventure released this 22 Feb 06:26
· 708 commits to master since this release

Release v0.11.0

Changes since 0.10.4:

  • Add: extensive updates to Builder features, installation, user guide and source code (#109). Updates captured in #79 and #80.
  • Add: creation of numerous example configurations (in /configs). Many supported displays and shields now pre-configured according to Table of TFT / OLED shields & breakout boards
  • Change: major simplification of configuration options, now specific to the display/touch combination
  • Change: extensive rewrite of touch & orientation handling (#96, #97, #98, #105), related fixes. Added touch pin detection, calibration and test sketches. Please refer to migration notes below.
  • Add: support for GPIO / keyboard controls (#66), M5stack buttons (#84)
  • Fix: many fixes in TFT_eSPI mode
  • Change: default font for RPi is now NotoMono-Regular
  • Add: support for images in RAM or Flash (#101)
  • Add: support for checkbox / radio button callbacks (#74)
  • Add: startup reporting of version and config modes (can be disabled with INIT_MSG_DISABLE)
  • Add: support for mcufriend (#87)
  • Add: support for HX8357
  • Add: support for HX8347D
  • Add: support for XPT2046_PS (from PaulStoffregen/XPT2046_Touchscreen)
  • Add: support for STM32 from STM, Arduino DUE, Arduino Zero
  • Change: default for fill attribute on ElemCreateBtnImg() / ElemCreateImg() changed to true to improve redraw performance
  • Fix: dynamic image updates (#91)
  • Fix: numerous miscellaneous fixes

Migration notes:

  • Users are strongly encouraged to start using the example configs instead of the legacy GUIslice_config_ard.h or GUIslice_config_linux.h. Please refer to How to Configure GUIslice
  • STM32 users with DRV_TOUCH_XPT2046: Need to select DRV_TOUCH_XPT2046_STM instead.
  • Resistive touch users (DRV_TOUCH_SIMPLE, DRV_TOUCH_STMPE610, DRV_TOUCH_XPT2046*) should run the new touch pin detection and calibration utilities. Please refer to Configuring Touch Support
  • Debug error messaging has now been enabled by default. This can be disabled (to conserve RAM once correct operation is confirmed) by setting DEBUG_ERR set to 1.