Posts by SEGGER - Jörg

Hi,

unfortunately the code snippet does not explain in detail what is the problem and what should be done.

Regards, Jörg

Hi,

The Unicode chapter (sub chapter of 'Language support') describes
exactly what needs to be done to get for example Japanese text on the
display. It describes how to enable UTF8-support. Once enabled, all text related functions automatically support UTF8-text.

Regards, Jörg

Hi,

Changing the preprocessor defines does not work without recompiling the libraries. If the touch is not required the PID-initialization should not be called.

Regards, Jörg

Hi,

Of course the ICONVIEW widget could be used. But unfortunately it is not possible to hide one or more dedicated icons. If an icon is not used it could be removed with ICONVIEW_DeleteItem() and inserted if required again with ICONVIEW_InsertXXXItem().

Regards, Jörg

Hi,

Maybe there is not enough memory available. Please refer to the documentation chapter 'PNG file support/Memory usage'.

Regards, Jörg

Hi,

The chapter 'The Window Manager (WM)/Callback mechanism, invalidation, rendering and keyboard input/Tiling mechanism' explains the reason for multiple WM_PAINT messages. The description of the function WM_CreateWindow() explains how to achieve only a single WM_PAINT message in the 'Style' table under WM_CF_LATE_CLIP.

Regards, Jörg

Hi,

An easy way would be using a TEXT widget. If the variable should be shown as part of the FRAMEWIN widget it should be drawn within the WM_PAINT event of the dialog callback function. Please also refer to the sample DIALOG_SliderColor.

Regards, Jörg

Hi,

The chapter 'Language Support/Arabic support' of the emWin documentation describes in detail how Arabic is supported by emWin. Of course it considers the character positions.

Regards, Jörg

Hi,

Unfortunately there is no ready to use widget for a filled graph. But that could be achieved by a window drawing the graph manually for example with vertical lines. There is a sample (MEMDEV_UseDataPointer) showing a very simple filled graph:

May that helps.

Regards, Jörg

Hi,

The parent window of the buttons window receives notification codes WM_NOTIFICATION_CLICKED and WM_NOTIFICATION_RELEASED from the buttons. To implement long press a timer could be used. If it is expired and no release has been detected in the meantime a long press occurs, if a button is pressed twice within a short period a double tap is detected.

Regards, Jörg

Hi,

The Unicode-implementation of emWin is based on UTF8. Because of that it is highly recommended to use UTF8-encoded text in emWin. The Unicode chapter (sub chapter of 'Language support') describes exactly what needs to be done to get for example Japanese text on the display.

Regards, Jörg

Hi,

If GUI_DEBUG_LEVEL is >= 4 the memory allocation module generates a warning:

if ((U32)Size > GUI_ALLOC__Context.NumFreeBytes) {
GUI_DEBUG_WARN("GUI_Alloc.c:\nNot enough memory available in _Alloc().");
return 0;
}

More information can be found in the documentation under GUI_X_ErrorOut(), GUI_X_Warn() and GUI_X_Log().

Regards, Jörg

Hi,

The code of the euro-sign is 0x20AC. Unfortunately that code is not part of the ASCII- or ISO8859-1 range. Here is a sample with a custom font showing the euro character:

#include "GUI.h"


GUI_CONST_STORAGE unsigned char acGUI_Font16_20AC[ 10] = { /* code 20AC, EURO SIGN */
  ___XXXX_,
  __X_____,
  _X______,
  XXXXXXX_,
  _X______,
  XXXXXXX_,
  _X______,
  _X______,
  __X_____,
  ___XXXX_};


GUI_CONST_STORAGE GUI_CHARINFO_EXT GUI_Font16_CharInfo[1] = {
   {   7,  10,   0,   3,   7, acGUI_Font16_20AC } /* code 20AC, EURO SIGN */
};


GUI_CONST_STORAGE GUI_FONT_PROP_EXT GUI_Font16_Prop1 = {
   0x20AC /* first character */
  ,0x20AC /* last character  */
  ,&GUI_Font16_CharInfo[  0] /* address of first character */
  ,(GUI_CONST_STORAGE GUI_FONT_PROP_EXT *)0 /* pointer to next GUI_FONT_PROP_EXT */
};


GUI_CONST_STORAGE GUI_FONT GUI_Font16 = {
   GUI_FONTTYPE_PROP_EXT /* type of font	*/
  ,16 /* height of font  */
  ,16 /* space of font y */
  ,1 /* magnification x */
  ,1 /* magnification y */
  ,{&GUI_Font16_Prop1}
  ,13 /* Baseline */
  ,7 /* Height of lowercase characters */
  ,10 /* Height of capital characters */
};


void MainTask(void) {
  GUI_Init();
  GUI_UC_SetEncodeUTF8();
  GUI_SetFont(&GUI_Font16);
  GUI_DispString("\xe2\x82\xac");
  while (1) {
	GUI_Delay(100);
  }
}

Regards, Jörg

Hi,

Unfortunately it is not possible to use emWin fonts higher than 255 pixels.

Regards, Jörg

Hi,

The display seems to work but the configuration of the driver seems to be not ok for the display. GUIDRV_SLin.h is not required if GUIDRV_FlexColor is used.

Regards, Jörg

Hi,

The test works (of course) without problems and fades from black to white.

Regards, Jörg

Hi,

Here you will find a sample using the SPI interface.

Regards, Jörg

Hi,

Please refer to the attached sample configuration file.

Regards, Jörg

Hi,

We don't think that splitting GUI_Exec1() will solve that problem. Some actions like drawing of large images could use more than 50ms anyhow (depending on the used hardware), also after splitting the function. Unfortunately emWin currently does not have a function which allows triggering a watchdog during longer operations. We may add a function in a later version.

Regards, Jörg

Hi Ezio,

The function GUI_SIF_SreateFont() fills the structure which is pointed by pFont. It does not changes the pointer itself. Do you work with a 16 bit CPU? Unfortunately we could not see any problem. Could you please provide a SIF file and a sample which shows the problem?

Regards, Jörg