Ok, I'll have to look and make sure the CGRAM programming can be done in 4bit mode and that we have all the needed pins available. Also a working code example (in any language) would be nice.
The other question -- translating from ascii to the LCD character set is as much a matter of philosophy as implementation. We currently send out the 8-bit char directly, untranslated. The representation (interpretation or display) of that char may differ on your computer and the LCD. Still, you only have to know how to generate an arbitrary ascii char and what character table in ROM is for your device. You don't have to guess how OWFS will mangle your chars. Translating between common formats would be trivial. The best approach from a design point of view would be to give the screen file a different name if there is translation involved. The only problem is in the added complexity. The first time user might be overwhelmed by all the different non-obvious choices. I don't mind doing it if there is consensus on the implementation, with a writeup explaining the mechanics for new users. Paul On Fri, Jan 28, 2011 at 12:35 AM, Roberto Spadim <[email protected]> wrote: > this's a feature request for owfs: *write 1 character bitmap to display rom* > ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
