NXTComm interface and exception propagation

This is where you talk about the NXJ software itself, installation issues, and programming talk.

Moderators: 99jonathan, roger, imaqine

NXTComm interface and exception propagation

Postby kirkpthompson » Mon Dec 24, 2007 6:14 pm

The NXTComm interface does not specify any Throws on the sendData and readData methods. The NXTCommBlueCove implementation catches any exceptions in these methods and spews them to STDERR. Are there any plans to change the interface (add the Throws) so that any exceptions can be managed by the implementor of the API?

I guess I could always change the printStream for STDERR to go to a sink...

Thnx.

-K
User avatar
kirkpthompson
leJOS Team Member
 
Posts: 304
Joined: Wed Dec 05, 2007 1:27 am
Location: New Mexico, USA

Postby bbagnall » Tue Dec 25, 2007 6:59 pm

Are you talking about iCommand? I've changed the next version (iCommand 0.7) so that you can catch this yourself. Should make it easier to build a more responsive GUI for iCommand projects.
User avatar
bbagnall
Site Admin
 
Posts: 392
Joined: Fri Aug 04, 2006 4:03 pm

Postby kirkpthompson » Tue Dec 25, 2007 7:14 pm

Hi, yes- package icommand.nxt.comm. Cool. I will look forward to it.
User avatar
kirkpthompson
leJOS Team Member
 
Posts: 304
Joined: Wed Dec 05, 2007 1:27 am
Location: New Mexico, USA


Return to NXJ Software

Who is online

Users browsing this forum: Majestic-12 [Bot] and 5 guests

more stuff