1. yes
2. I can see I'm new to Jal. Explain byte*x please
3 My org. thought was the same but why ( you pointed out once ) not
read from the display.
Why not make it a choice?
4. You are right. It will be done
On 16 Dec., 03:38, mattschinkel <[email protected]> wrote:
> Just some notes after looking at your new code. again, only
> suggestions.
>
> 1. print_char & print_char_i could become one procedure. A constant or
> variable (the user can decide in his sample) could set what direction
> a character is printed. A constant can tell the library how the font
> array is set-up (see my notes above).
> 2. my glcd is > 256 pixels (240x320), therefore I can't draw anything
> in the rest of my screen with your procedures. I had put a fix into
> glcd_common (byte*x in var)
> 3. Maybe glcd_common_graphics_X01.jal could be renamed and made into
> glcd_cache? the current name suggests that it draws graphics (like
> line, circle, etc).
> 4. glcd_Nokia_3310_X01.jal, glcd_Samsung_KS0108_X01.jal should have a
> procedure like lcd_write_pixel(byte in x,byte in y,byte in color). All
> other libraries have this. If all libraries are the same, they can all
> use the same procedure to draw things.
>
> Of course, maybe my code and thinking is wrong. If it is, let me know
> and I can throw it out the window.
>
> Matt.
--
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.
