1) If you go from GLCD to the compiler and save one of the files as a backup copy, or for that matter add any .c file to the directory that has the _main.c _events.c etc., the application will crash with an out of bounds error. It appears that it tries to read in all the .c files or their names and only expects the quantity it generated to be present. Adding a sub directory is ok.
I didn't reproduce this report. Can you send me some screen-shot or something else in order to reproduce this issue?
2) If you highlight an object (a button for example) and scroll down, the red box is mis aligned.
3) The misalignment makes it impossible to drag objects to the top or bottom of the screen.
5) A screen full of labels that touch each others, such as laying out 7 labels for 7 lines of help text results in the code for the click events not being called.
6) A square button can go to the top of the screen while a text button requires a 3 pixel border. If you drag them to the bottom of the screen, usually the square button can be dragged partially off the screen a little further than a text button. None of the objects should be dragged off the screen. It also forces the user to reset the coordinates in the dialog box so that the objects can be dragged with the mouse again.
7) The 3x5 fonts cause corruption of the design screen. Only a few of the letters display. For example, "Your text Here" might become just "Y". Changing the font back to 5x7 restores the text.
Reproduced, and reported to our developers. They will try to fix it for next release.
4) There seem to be some memory overwrite issues that cause the grid representing the pixels to be corrupted. The only way around it is to reload the project. I notice that changing the max length parameter from its default of zero seems to help, but not always. It may have just been a coincidence.
can you clarify your question, because I didn't understand it correctly ?