> Setting the mode is only required once.
> Why not try simple text without parsing?
> Parsing is unlikely to work in any event because you are not sending
> a string. It will, at best, apply to the first character.
>
> I don't see a .string property for the oI2C object in the V6
> documentaton. It DID exist in V5.
>
> So, we could write things like:
> screen.string = "Hello World!"
>
> Unfortunately, V6 won't accept it!
>
> Richard
>
>
I hadn't noticed the loss of that .string. I know that oEEPROM
accepts .string, so you could "spoof" the system and call the device a
oEEPROM object and turn off the increment. Then try using .String on
that object. Another way you could do this would be to use the oBuffer
object, set that to a string and access the individual bytes by index.
Caveat, I've not tried this yet, but it should work.
DLC
--
------------------------------------------------------
Dennis Clark ooPIC Tech Support
www.oopic.com
------------------------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/oopic/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/oopic/join
(Yahoo! ID required)
<*> To change settings via email:
mailto:oopic-digest@yahoogroups.com
mailto:oopic-fullfeatured@yahoogroups.com
<*> To unsubscribe from this group, send an email to:
oopic-unsubscribe@yahoogroups.com
<*> Your use of Yahoo! Groups is subject to:
No comments:
Post a Comment