I FINALLY wrote some data to the LCD!! YAY !!! I was trying to get the
python application to work.. without any luck.. but I ended up going ahead and
trying Zadig changing the driver to libusb-win32... After I gave up on Python,
I went back to FPC and just ran my existing sample program, an
I know, that this task is heavy and should be only performed by The
elites among Pascal programmers not by users of this programming
language. But I Am sure, that if somebody experienced will answer. on my
question, it would increase The number of volunteers, who would be ready
to generate newe
On 8/21/19 8:30 AM, James Richters wrote:
I FINALLY wrote some data to the LCD!! YAY !!! I was trying to get the python application to work.. without any luck.. but I ended up going ahead and trying Zadig changing the driver to
Persistence pays off. Congrats!
Also I need to stick a $06
Well.. It doesn’t always work just reading constantly and writing in a
different thread..
So I have my fast read loop always reading then my LCD write loop sending the 3
packets every 0.3 Seconds.. and it functions ok, and I don’t miss too many
counts... but every so often I get this message:
Thanks for the suggestion!
James
>Move(LCD_Array[0..6],Device_Array[1],7)
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Hi!
Am Montag, den 19.08.2019, 18:22 -0400 schrieb James Richters:
> Oh, for some reason I wasn't thinking I was replacing mydevice.pas
> with snapi.pas... Ok.. so if
> I understand this correctly, make the changes necessary in snapi.pas
> to use libusboop.pas instead of the old usb.pas, and th
Hmm I'll see what I can come up with. The language of all these units is
completely foreign to me. I really don't understand how constructors and this
inherited stuff or how even the functions and procedures manage to get anything
done. I've been programming with Pascal since Turbo Pascal bac
From your example it looks like you placed the device reading
(interrupt read) and writing (set report) into the same read thread. I
thought keeping them separate was a good idea: tight loop reads and
less frequent writes (LCD updates).
Libusb is supposed to be thread-safe. Not really an issu
I had them separated, but whenever it happened that I tried to write while it
was waiting to read, I would get the error below. If it was reading all the
time it seemed fine.. just if it was idle waiting to read and I did a write
that it would fail with EAccessViolation: Access violation
I put
On 8/21/19 6:35 PM, James Richters wrote:
I had them separated, but whenever it happened that I tried to write while it
was waiting to read, I would get the error below. If it was reading all the
time it seemed fine.. just if it was idle waiting to read and I did a write
that it would fail w
10 matches
Mail list logo
