Hello Ralph, 1. I believe gx_widget_previous and gx_widget_next are not application options as they're defined when widget is created to provide a doubly-linked list between all widgets. Overriding this manually will break references and could lead to errors inside event and draw handlers. If you'd like to return to the previous window, why not have a global GX_WIDGET pointer. When GX_EVENT_HIDE is called, a window assigns its own pointer to the global one so you can always keep track of what was the previous window. Alternatively, you can create new window and attach it to the old one, meaning that when you eventually hide it, you will return to its parent which was the previous window. 2. GUIX only provides rendering engine and outputting video data needs to be handled by the application. On Synergy, this is done by GLCD Controller. Specifying target platform allows GUIX Studio to generate a configuration file that points to the accelerated drawing functions (default GUIX uses software rendering) - for Synergy it's D/AVE2D and JPEG acceleration, on ST it's ChromeArt & etc. ILI9163V is a video output controller, so its implementation should be done on the application level (since it does what our GLCDC would do). In this case, specifying target platform as "Generic" and providing pointer to your own buffer-toggle (i.e. rendering) function when calling GUIX studio display initialization should be enough to get it running. Provided you configured the relevant interface (I'm assuming SPI) and created a function capable of writing pixels to the display, Ilitek controller should run fine on Synergy. Regards
↧