Hi Matt,
On 2015-09-16 02:47, Matthew Schinkel wrote:
Personally I think these libraries need to be modified to align with
our style guide. Procedures like procedure glcd_write_pixel() are
defined in several different libraries, but procedure and variable
names should be unique in each library.
The fix I suggest is to use alias before including the glcd_common
library, to rename these procedures. For example:
alias glcd_line is T6963_line
alias glcd_write_pixel is T6963_write_pixel
include glcd_common
The last should be probably preceded by "include t6963", but otherwise
this seems like a good method.
While I'm still working on some extensions of the t6963 library I may as
well adapt it to this naming convention: change all glcd_ prefixes into
t6963_ and add aliases to the sample program.
This will:
1. allow the user to choose what "draw line" and other procedures to
use (the device lib, or glcd common)
2. allow 2 or more lcd libraries to be used
3. align with our standards
W.r.t. '2': I think using 2 glcds of the same type would still be
impossible.
From the images, T6963 appears to be better since there are no blank
spaces between characters. With KS0108, you can see blank spaces even
if you are doing only graphics. I can also find bigger T6963 displays
on ebay (240x128 looks nice).
I have searched for a 240x128 display for a test of the t6963 library
but didn't find one within my budget.
Regards, Rob.
--
*Rob H*amerling - http://www.robh.nl
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/jallib.
For more options, visit https://groups.google.com/d/optout.
