On Fri, 17 Jan 2003, [ISO-8859-1] Roger Lindsjö wrote:

>I'd rather have setData(data) that uses offset 0, and length data.length 
>and a setData(data, offset, length) than separate setPfset and setLength 
>methods.

ah, good idea!  I think there should still be seperate setters also, 
though; but having 2 setData() methods is good and makes it clear that one 
way you care about offset/length, and the other you don't...

>  I have two problems, I keep getting a lot of NullPointerExceptions 
>from the javax-usb-ri/src/com/ibm/jusb/UsbEndpointImp.java there the 
>wrapped UsbEndpoint is null.

there shouldn't be any wrapped UsbEndpoint...do you know what method is 
failing?

>Also, when just getting the topology from my hubs and my printer 
>everything works fine, but when connecting my Xanboo box the JVM dies 
>due to a signal 11 in the native code and I'm trying to resolve why.

probably related to the naming changes...can you tell what function is 
failing?
Also I'm going to fix-up the JNI so each call is 'checked', i.e. each JNI 
call will make sure it didn't fail by cehcking for an Exception, which 
should put an end to all the Sig 11 problems...



-- 
Dan Streetman
[EMAIL PROTECTED]
---------------------
186,272 miles per second:
It isn't just a good idea, it's the law!


-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your
clients even if they use browsers that are limited to 40 bit encryption.
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
_______________________________________________
javax-usb-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/javax-usb-devel

Reply via email to