On Mon, 2019-08-19 at 03:11 +0200, Marc Santhoff wrote:
> Hi James,
>
> are you really sure the WHB04B-6 is exactly the same as your WHB04B-4 viewn to
> the USB API?
>
> If those thingys come with a dll, maybe you can compare the header files?
> If there is no header file you could ask the manufact
My concern was that I could not read and write at the exact same time
-Original Message-
From: fpc-pascal On Behalf Of Stefan
V. Pantazi
Sent: Sunday, August 18, 2019 9:32 PM
To: fpc-pascal@lists.freepascal.org
Subject: Re: [fpc-pascal] USB Human Interface Devices
>> My guess is th
They come with a little CD, but not much really useful on them.. mostly
instructions on how to get them to work with Mach3. But the manual does cover
both models. The only difference is one has a selection switch for 4 axis and
the other has one for 6 axis, but the 4 axis version shows 6 axis
My guess is that it would be better to leave the time sensitive read
thread to do the fast reads and immediate calculations and leave writing
to the device screen in a separate thread (even main thread), with a
lower update frequency!
Yes, that was what I was attempting to describe.. but I can't
Hi James,
are you really sure the WHB04B-6 is exactly the same as your WHB04B-4 viewn to
the USB API?
If those thingys come with a dll, maybe you can compare the header files?
If there is no header file you could ask the manufacturer for it. If they made
a programm using that dll, there must be a
>>Assuming there are no other bugs in the libusbxhid library, for writing data
>>you have to guess the reportType (in, out, feature) and reportNum parameter
>>and set the report data buffer correctly (first byte is the report number)
>>for your device. Have a look at similar devices.
I don't kn
On 8/18/19 3:58 PM, James Richters wrote:
As far as reading it goes, things are going pretty well.. I still have yet to write to
the display.. I can't get any of my attempts to send data to it to be successful at all..
I get "control transfer to usb device failed!"
Assuming there are no othe
As far as reading it goes, things are going pretty well.. I still have yet to
write to the display.. I can't get any of my attempts to send data to it to be
successful at all.. I get "control transfer to usb device failed!"
Thanks for the advice on a thread safe queue!
For the moment I've bee
On 18/08/2019 10:43 am, Michael Van Canneyt wrote:
> One wonders why these README files are created. No-one seems to read them
> anyway.
Yeah, I've been wondering that same thing for years. Maybe we should
create a README.1st file. :-P
Regards,
Graeme
--
fpGUI Toolkit - a cross-platform G
James,
From the looks of it you made good progress reading the hardware and
using a dedicated thread for it. Congrats! Seems you're in the thick of
it now ready to get the minute details sorted out.
Anyway, just a heads up that concurrent programming (threads,
synchronization, etc) has many
I have a question about USB data transfer.. but it's going to take some
explanation...
I've been doing more testing with my device and Libusbxhid. Here's the device:
https://www.amazon.com/gp/product/B07M5ZY1P2
I have all the inputs working, still have to figure out how to output to the
LCD
Is it possible to remove or clear items from TFPSList without actually
shrinking the memory (i.e. setting capacity to 0)? Looking the source below I
see every time I clear the list it the capacity is set to 0 also. This is fine
most of the time unless you want to reuse the list without reallocat
I just pushed it.
>Could you please "git push" the source code to Github so that the line numbers
>match the output? At least in line 1330 of libusboop.pas there is no Create.
>Please ensure that the
>version on Github is the very same version where you executed the program and
>got the line
Op 2019-08-18 om 11:43 schreef Michael Van Canneyt:
On Sat, 17 Aug 2019, leledumbo via fpc-pascal wrote:
How are the FPC RTL documentations generated? I wanted to see if I
could
generate .docsets files from them also.
A starting point: https://wiki.freepascal.org/FPCDocs_Tutorial
I believe
On 18/08/2019 15:47, Dmitry Boyarintsev wrote:
> RawByteString?
RawByteString still has a dynamic code page. Additionally, operations on
RawByteString are not very well defined by Embarcadero. In general, it
should only be used as a function result or parameter type, and never as
a variable on whi
RawByteString?
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
Hi!
Am Samstag, den 17.08.2019, 18:00 -0400 schrieb James Richters:
> I commented out all the try & except stuff and ran it.. I get this
> output:
Could you please "git push" the source code to Github so that the line
numbers match the output? At least in line 1330 of libusboop.pas there
is no Cr
On 18/08/2019 11:57, Gabor Boros wrote:
> I do not want to fight with "char"s or "byte"s. Just want to use the
> easier way which have the best performance. (The original code use
> strncpy.) I can use "s_n:String[sn_len]", but "String" is ShortString
> and it's have CP_ACP codepage if I understand
Hi All,
I try to rewrite some C/C++ code with FPC. I don't know which is the
best string handling technique in this case. The original code for example:
char b_l[b_list_len][bn_len+1];
char s_n[sn_len+1];
I do not want to fight with "char"s or "byte"s. Just want to use the
easier way which
On Sat, 17 Aug 2019, leledumbo via fpc-pascal wrote:
How are the FPC RTL documentations generated? I wanted to see if I could
generate .docsets files from them also.
A starting point: https://wiki.freepascal.org/FPCDocs_Tutorial
I believe that "write me" part is not far from calling make wit
20 matches
Mail list logo
