ToDo - olikraus/m2tklib GitHub Wiki

issue create menu tutorial. explan m2_SetRoot (better m2::setRoot) and M2_EXTERNAL_... reuse pics from touch screen_

issue 41 (on Google Code)

check and document BUTTONPTR and LABELP

Oct 6, 2012 Delete comment Project Member #1 olikraus

BUTTONPTR is used by the new Bookmarks.pde example LABELP is not used at all. Needs testing

Oct 6, 2012 Delete comment Project Member #2 olikraus

(No comment was entered for this change.)

Status: Started Labels: -Milestone-Future Milestone-1.10 Feb 16, 2013 Delete comment Project Member #3 olikraus

LABELP added, needs to be tested on Arduino LABELP --> documentation exists BUTTONPTR --> documentation exists

--> can be closed

issue 88 (on Google Code)

m2el2lmenu.c contains new element X2LMENU

  • tests implemented (sdl)
  • Todo: Documentation? Example

issue 90 (on Google Code)

add elements to draw lines and frames TODO: implement and test M2_HLINE, M2_FRAME requires new graphics methods?

#define M2_GFX_MSG_DRAW_HLINE 					3
#define M2_GFX_MSG_DRAW_VLINE 						4
#define M2_GFX_MSG_DRAW_BOX 						5


    case M2_GFX_MSG_DRAW_HLINE:
      u8g_DrawHLine(m2_u8g, arg->x, m2_u8g_height_minus_one - arg->y, arg->w);
      break;
    case M2_GFX_MSG_DRAW_VLINE:
      u8g_DrawVLine(m2_u8g, arg->x, m2_u8g_height_minus_one - arg->y, arg->h);  
      break;
    case M2_GFX_MSG_DRAW_BOX:
      m2_u8g_draw_box(arg->x, arg->y, arg->w, arg->h);
      break;


void m2_gfx_hline(uint8_t x0, uint8_t y0, uint8_t w);
void m2_gfx_vline(uint8_t x0, uint8_t y0, uint8_t h);
void m2_gfx_box(uint8_t x0, uint8_t y0, uint8_t w, uint8_t h);

hline, vline and box are not used at the moment

m2elspace can be extended to support this --> box inside m2elspace.c M2_BOX(el, fmt)

--> Documentation done, sdl example finished

issue 91 (on Google Code)

touch screen support:

  • Add key as argument to the element itself. --> DONE
  • Remove k option completly --> DONE
  • Add xbm elements --> DONE
  • Dokumentation --> DONE
  • Examples (probably not required?)

issue 95 (on Google Code)

it seems that the combination of two problems has cased the elements to appear almost corrct, but lead to a one-pixel-shift upwards.

Problem 1 (all specific u8glib gh files): Frame/Box calculation. M2tklib has the origin at the lower left, but u8glib at the upper left. Pixel translations: y = height - 1 - y

for a box with height h the upper left corner (u8g coordinates) is y = height - 1 - ( y + h - 1 ) actually the "- 1" is missing this gives y = height -1 - y - h + 1

Problem 2 (m2ghu8gutl.c, m2ghu8gicon.c): u8g text alignment is "Bottom", but lowest pixel is one pixel above bottom line this means, drawing at y (m2tk coordinats) will draw the lowest pixel at y+1 (m2tk coordinates)

these two problems make the elements appear correctly: Both the frame and the text are shifted up by one pixel, which is wrong in both cases.

Labels: -Milestone-Future Milestone-1.10 Jan 13, 2013 Delete comment Project Member #3 olikraus

XBM has to be checked also

Jan 13, 2013 Delete comment Project Member #4 olikraus

tests:

  • small data entry (underline)
  • xbm

Jan 13, 2013 Delete comment Project Member #5 olikraus

it seems that only changes are required to m2ghu8gutl.c and m2ghu8gicon.c

as of now, all changes done what about the vertical scroll bar???

tests:

  • small data entry (underline)
  • xbm
  • vsb <<<<<<< local

no problem seen with sdl

--> can be closed

DISABLE ELEMENT

M2_HIDE implemented, but not yet tested