This Forum is Dedicated For all The Object Oriented PIC Lovers .......... The concept behind OOPic is straight forward. Use preprogrammed multitasking Objects from a library of highly optimized Objects to do all the work of interacting with the hardware. Then write small scripts in Basic, C, or Java syntax styles to control the Objects. During operation, the Objects run continuously and simultaneously in the background while the scripts run in the foreground telling the objects what to do.

Monday, January 28, 2008

Re: [oopic] Re: NC2004A LCD Screen with Modtronix LCD2S daughter board

A reply to remove my last reply. I had a momentary brain fart -
although the .String property was listed in the oEEPROM and oI2C it did
not work. So it appears that the .String was simply removed since it
must have been resource intensive to fix.

DLC

rtstofer wrote:
> --- In oopic@yahoogroups.com, ooPIC Tech Support <dennis.clark@...>
> wrote:
>
>> rtstofer wrote:
>>
>>> 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
>>
>>
>
> The 'old' oEEPROM had a .string property but the new one doesn't.
>
> Using the oBuffer approach doesn't allow a 'prefix' byte to cause the
> entire string to be 'parsed'. There is a command for this LCD that
> will do neat things like interpret ('parse') "\nHello\tWorld!\n"
> doing the CR LF things as expected.
>
> But, it probably only works if it is the first byte in a long
> string. Terminating the transaction after every char ('stop'
> condition) would probably defeat the process. I suppose using
> cv10bit and sending the command followed by a single character MIGHT
> work but it is a lot of traffic.
>
> I don't understand why the .string properties were removed. You
> know, V5 may live forever!
>
> Richard
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>

--
------------------------------------------------------
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:

http://docs.yahoo.com/info/terms/

No comments: