java-player-users

[Java-player-users] requestInterface() restrictions

[Kurt K. <kon...@AI...>]

Hmm, not much traffic on this user group...

requestInterfaceXXXX() functions can't be called after runThreaded() is 
invoked, they hang or return the wrong result, or do other bad things 
like run out of heap space if called repeatedly.

Cheers --Kurt

Re: [Java-player-users] requestInterface() restrictions

[Radu B. R. <ru...@cs...>]

Yup, you're right Kurt, that part needs to be recoded.

There was an earlier mail from Shawn Lavelle a couple of weeks ago about the problem of 
requesting interfaces.

R.

Kurt Konolige wrote:
> Hmm, not much traffic on this user group...
> 
> requestInterfaceXXXX() functions can't be called after runThreaded() is 
> invoked, they hang or return the wrong result, or do other bad things 
> like run out of heap space if called repeatedly.
> 
> Cheers --Kurt

-- 
| Radu Bogdan Rusu | http://rbrusu.com/
| http://www9.cs.tum.edu/people/rusu/
| Intelligent Autonomous Systems
| Technische Universitaet Muenchen

Re: [Java-player-users] requestInterface() restrictions

[Radu B. R. <ru...@cs...>]

Of course, I forgot to mention that you can always just create a new instance of 
PlayerClient to the same port on your robot and request that additional device. A bit of a 
hack but it should work.

So, something along the lines of:
...
PlayerClient robot1 = new PlayerClient ("localhost", 6665);
PtzInterface ptzi1  = robot1.requestInterfacePtz (0, PlayerConstants.PLAYER_OPEN_MODE);
robot1.runThreaded (-1, -1);
...
PlayerClient robot2 = new PlayerClient ("localhost", 6665);
PtzInterface ptzi2  = robot2.requestInterfacePtz (1, PlayerConstants.PLAYER_OPEN_MODE);
robot2.setNotThreaded ();
..
R.

Radu Bogdan Rusu wrote:
> Yup, you're right Kurt, that part needs to be recoded.
> 
> There was an earlier mail from Shawn Lavelle a couple of weeks ago about the problem of 
> requesting interfaces.
> 
> R.
> 
> Kurt Konolige wrote:
>> Hmm, not much traffic on this user group...
>>
>> requestInterfaceXXXX() functions can't be called after runThreaded() is 
>> invoked, they hang or return the wrong result, or do other bad things 
>> like run out of heap space if called repeatedly.
>>
>> Cheers --Kurt
> 

-- 
| Radu Bogdan Rusu | http://rbrusu.com/
| http://www9.cs.tum.edu/people/rusu/
| Intelligent Autonomous Systems
| Technische Universitaet Muenchen

Re: [Java-player-users] requestInterface() restrictions

[Radu B. R. <ru...@cs...>]

Okay, fixed this one too (I think).

I am committing everything to the SVN now, so please check them out later and test to see 
if they work.

For Shawn: I added a few extra checks, so when you request a certain interface, Javaclient 
should never return another one.

Cheers,
Radu.

Kurt Konolige wrote:
> Hmm, not much traffic on this user group...
> 
> requestInterfaceXXXX() functions can't be called after runThreaded() is 
> invoked, they hang or return the wrong result, or do other bad things 
> like run out of heap space if called repeatedly.
> 
> Cheers --Kurt

-- 
| Radu Bogdan Rusu | http://rbrusu.com/
| http://www9.cs.tum.edu/people/rusu/
| Intelligent Autonomous Systems
| Technische Universitaet Muenchen

Re: [Java-player-users] requestInterface() restrictions

[Shawn L. <sla...@at...>]

Hey Radu!
   Thanks for all your work today!  We'll get to checking it out early 
next week and let you know how things turn out.

   ~ Shawn

Radu Bogdan Rusu wrote:
> Okay, fixed this one too (I think).
> 
> I am committing everything to the SVN now, so please check them out later and test to see 
> if they work.
> 
> For Shawn: I added a few extra checks, so when you request a certain interface, Javaclient 
> should never return another one.
> 
> Cheers,
> Radu.
> 
> Kurt Konolige wrote:
>> Hmm, not much traffic on this user group...
>>
>> requestInterfaceXXXX() functions can't be called after runThreaded() is 
>> invoked, they hang or return the wrong result, or do other bad things 
>> like run out of heap space if called repeatedly.
>>
>> Cheers --Kurt
>