If
> that's so, then a bug report in the QCC would be in order.
>
> I hope either Sarah or Phil will see this, since they are the serial/USB
> experts here. Maybe they have some comments to add or a workaround they've
> discovered.
>
- Original Message -
F
> The identical script loaded in pre-windows 7 Livecode releases work.
>
> Thanks
> Camm
>
>
>
> -Original Message-
> From: use-livecode-boun...@lists.runrev.com
> [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Dar Scott
> Sent: 13 May 201
...@lists.runrev.com
[mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Dar Scott
Sent: 13 May 2012 05:43
To: How to use LiveCode
Subject: Re: Serial Comms in 4.6.4
Hi, Camm!
I don't remember any changes.
Maybe this can be tracked down. What OS? How does it fail?
However, you might wa
Hi, Camm!
I don't remember any changes.
Maybe this can be tracked down. What OS? How does it fail?
However, you might want to rule out other things. I find the most common
reason that a serial communications program suddenly fails is a cable issue.
Usually the handshake lines don't make it
Has something changed in the use of open , close , read , write driver
and/or SerialControlString string in version 4.6.4.
I have a stack for serial comms that works fine if run in older versions of
Livecode , but fails to read in version 4.6.4
Same script ??
Regards
Camm
__
