No doubt you are right, but, worst comes to worst, if it can act just like a
comm port, I can transfer and/or control ANYTHING - and I have with comm
ports. It's all about how MY software at both ends, interprets it. Comm port
drivers are already available. Now it doesn't have to be a comm. port driver
that's used. Hell, if we can transfer bitmaps that'll work too. A TColor
object is just another word for an __int32 word. If I control the meaning of
both sides of the interface, i.e. the camera & the camera operating
software, the bits in that TColor pixel mean whatever I damn well want them
to mean.
I'd send you some examples, but what I have was written to control test
equipment for cellular site technical evaluations. Point is, I didn't write
drivers. I simply used drivers that were already available for purposes
other than for what they were intended. The transport equipment & software
(including drivers) didn't care what data was being transmitted.
Bob...
---------------------------------------------------------------------
I don't mind if you don't like my manners.
I don't like them myself. They're pretty bad.
I grieve over them on long winter evenings.
-- Humphrey Bogart, "The Big Sleep"
-----Original Message-----
From: Godfrey DiGiorgi
Sent: Monday, January 31, 2011 3:52 PM
On Mon, Jan 31, 2011 at 3:04 PM, Robert Blakely <b...@blakely.com> wrote:
> Data is data & packets is packets. The writer gets to determine what's in
> the packets & how to use that information.
That's my nomination for the "just about pure nonsense" quotation of
the day on PDML.
Remind me not to hire you to develop a USB driver.
--
PDML Pentax-Discuss Mail List
PDML@pdml.net
http://pdml.net/mailman/listinfo/pdml_pdml.net
to UNSUBSCRIBE from the PDML, please visit the link directly above and follow
the directions.
