Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: [lpc2000] Re: Using Hantronix Chip on glass technology LCD Modules

2006-05-24 by Tom Walsh

wickedmonster2002 wrote:

>Wow, i feel like i m being grilled for murder.
>
>  
>
And, um, you thought that writing embedded code was as easy as Visual Basic?

TomW

>--- In lpc2000@yahoogroups.com, newmanrf@... wrote:
>  
>
>>You have to tell us what you have to work with so that we can help you
>>with the shortest possible path. Since you did not I'm going to
>>interrogate you but eventually I'll get tired and abandon this
>>    
>>
>thread. So
>  
>
>>here goes:
>>
>>1) You said you already had code working. Is that the glcd code?  Does
>>your working code use the header gdisp.h?  If you have gdisp.h then your
>>working code uses glcd from somewhere other than 8052.com. Tell us
>>    
>>
>if your
>  
>
>>code has gdisp.h in it.
>>    
>>
>
>
>No! It does not have gdisp.h in it.
>
>
>
>  
>
>>2) If your using glcd code (the one with gdisp.h in it)  then it already
>>has font files and they are available for you to use. I will wait to
>>demonstrate how to use them based on your answer to question 1.
>>    
>>
>
>
>See question 1.
>
>  
>
>>3) If your NOT using glcd then the shortest path to success is the url
>>which I previously gave you. Here it is again:
>>http://www.8052.com/users/mkaras/GraphLCD.phtml
>>This gLCD code does what you want to do: Write text characters to the
>>display using a font which is already specified in the headers and he
>>shows you how to use them. In this scenario there is no reason to
>>    
>>
>use your
>  
>
>>existing font files or explain how to get your compiler to point to them
>>because the examples show you how.
>>    
>>
>
>
>Yes. I saw that. I will try doing that next.
>
>
>
>  
>
>>Wait!  Are you telling me the code from MKaras from 8052.com is complex?
>>Please say no. 
>>    
>>
>
>
>Okay. No. I dont find the code complex. Its a bit easier on the eyes.
>I said the glcd.c with the gdisp.h in it was complex. You must have
>misunderstood. Sorry about that.
>
>
>
>If you want complex and no documentation then buy  gLCD
>  
>
>>from Ramtex and write me back. The code is at least 30 times the size,
>>with lots of features like windowing, and harder to get started with.
>>There are at least 60 files in the Ramtex distribution of gLCD.
>>
>>Finally- Are you telling us that what you really want is a example
>>    
>>
>simpler
>  
>
>>than the gLCD code from mkaras off the 8052 site? 
>>    
>>
>
>I think its simple enough. I have zero experience in graphic displays.
>I had no idea we had to use fonts. I even interpreted fonts as
>something coming off the Windows operating system, a complete layman
>view. Laugh at my intelligence but you know, I gotta start somewhere.
>
> In my opinion that
>  
>
>>would be what you started with, the example that displays a bitmap. Want
>>to display simple characters crt style?  The answer, with this
>>    
>>
>display, is
>  
>
>>you have to use a font file and stuff it out rows at a time, 5 rows of 8
>>bytes for each character and then add some for intercharacter
>>    
>>
>spacing. Its
>  
>
>>not as simple as writing a character to a serial port or calling printf
>>but if you get the code working you can encapsulate all the non-trivial
>>stuff behind printf or debug_printf and your life is easy until you
>>    
>>
>start
>  
>
>>using another graphic display. Work like this takes work and the
>>    
>>
>gLCD code
>  
>
>>off of 8052.com is the shortest path to plugging and playing.
>>
>>Again, I hope this helps and if you have more questions just continue
>>posting them.
>>    
>>
>
>Thanks a lot. That site really helped.
>
>M.
>
>
>  
>
>>Richard Newman
>>Pittsburgh PA USA
>>
>>    
>>
>
>
>
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>  
>


-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.