It sounds like a version conflict, have you also grabbed the CVS version of stage and built it against the CVS player, also make sure some other version of player/stage is not getting picked instead of the one you intend when you build/run it.

Toby

On 27/09/2007, Paul Osmialowski <newchief@king.net.pl> wrote:
Hi,

Recently I'm trying to use CVS version more often and it still causes me
new troubles.
On 2.0.4 I was using such a piece of client-side C++ code to change Laser
configuration on Stage:
laser->RequestConfigure(); // get current configuration, since we want
some settings (i.e. Intensity) to remain untouched
laser->Configure(min_angle, max_angle, scan_res, range_res,
laser->IntensityOn());

I was trying to do the same on CVS version of Player/Stage (with
additional parameter for Configure, as new API requires):
laser->RequestConfigure();
laser->Configure(min_angle, max_angle, scan_res, range_res,
laser->IntensityOn(), laser->GetScanningFrequency());
It fails on client side with these error messages:
playerc error   : got NACK from request
terminate called after throwing an instance of 'PlayerCc::PlayerError'
panic: Aborted -- stopping myself...

On the server side it says:
warn: stage laser doesn't support message 3:5. (p_laser.cc ProcessMessage)
warning : Unhandled message for driver device=16777343:6665:laser:0
type=request subtype=5 len=0

closing TCP connection to client 0 on port 6665
All Stage drivers have been shutdown.

...and the server side is still able to accept new connections.

For both cases I was using everything.cfg world file.

Cheers,
Paul


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Playerstage-developers mailing list
Playerstage-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/playerstage-developers



--
This email is intended for the addressee only and may contain privileged and/or confidential information