Hi Mat I have tried to cook up a solution for Nokia type displays the 3 updated files end with 101217
The solution uses a cache when the user chooses by defining const GLCD_USE_CACHE I have chosen to place clear_cache & glcd_update in the graphics lib. I did that to keep the Nokia lib free from 'pollution'. In this way it has a clean interface with only the glcd_write_pixel proc Hope it can be useful Paul On 17 Dec., 00:08, mattschinkel <[email protected]> wrote: > All lcd's support writing pixels. I believe your write_pixel procedure > is currently named plot_pixel, but it should be renamed. This > procedure is to set one pixel on the screen. > > Some don't support reading pixels, and so there should be no procedure > defined which is ok. A library can use "if defined(lcd_write_pixel) > then" > > Matt. > > On Dec 16, 3:02 pm, pdhaene <[email protected]> wrote: > > > > > > > > > 3310 cannot be read from the display which gives a problem for > > writing per pixel > > > 1 should an empty procedure be in the file > > or > > 2 should it check for the presence of a cache. > > if so all writing has to be done in cache before updating > > or > > 3 should write_pixel() be left out for a lcd not supporting pixel > > writing > > > If 1 would it make sense to have a procedure e.g. use_cache( yesno ) > > to create and initialize such -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
