Yes if I set it to zero so it never times out, it never happens.. but then I
have the crash when I try to write. The same thing happened if I set it to 20
seconds... but I can only find out about it if I disable the write... if I put
the write in the read loop thread, then I have to have the
I suspect when the timeout time has been reached interrupt_read is calling
libusb_cancel_transfer to stop waiting for the transfer. It seems likely that
what's happening is that once in a while it tries to cancel the transfer, but
before libusb_cancel_transfer has a chance to cancel it,
>I added libusbhid_test_with_thread.pp to github. In that test you will notice
>I also attempted to test sharing across threads a data structure with
>(hypothetical) pen positions, using critical sections. Seems to work ok, but
>more testing is needed to make sure there are no problems.
Thank
I added libusbhid_test_with_thread.pp to github. In that test you will
notice I also attempted to test sharing across threads a data structure
with (hypothetical) pen positions, using critical sections. Seems to
work ok, but more testing is needed to make sure there are no problems.
The way I
On 22/08/2019 20:15, Zoë Peterson wrote:
> I just updated to the newer Cocoa headers (Thanks Jonas!) and I've run
> into a problem with Lazarus.
>
> NSExtensionContext.inc includes this line:
>
> {$if
> defined(__OBJC2__)defined(interface)defined(NSExtensionContext)defined(NSObject)}
>
>
> It
I just updated to the newer Cocoa headers (Thanks Jonas!) and I've run
into a problem with Lazarus.
NSExtensionContext.inc includes this line:
{$if
defined(__OBJC2__)defined(interface)defined(NSExtensionContext)defined(NSObject)}
It compiles ok for some reason, but screws up Code Tools so
That sounds like exactly like what I was trying to do.. would you mind sending
me your graphic tablet test? Maybe I can learn something from seeing how you
do things.
I just noticed I am always getting :
device attempting go clear halt on ep $81
libusb: error [winusbx_clear_halt] unable to
