Re: [FreeWRL-develop] Testing > scenefile from .fwplay

[Paulo E. C. <pau...@gm...>]

On 06/06/13 23:32, doug sanden wrote:
> A) generate .fwplay
> freewrl 1.wrl -R -N fly2
> (then hit "`" to toggle logging on, then off, hit 'x' to snapshot, hit 'q' to quit)
> creates:
> /recording/fly2.fwplay
> /freewrl_tmp/freewrl.snap.0001.bmp
> /freewrl_tmp/logfile.log
> .
The recording seems to be working well but....
"`" - I can't see any logging whatsoever as my keyboard is PT and 
triggering a "`" involves a combination of Shift+and another key.
So perhaps I'm not triggering the logging correctly.
Hitting "x" for a snapshot generates a png file and not a bmp.
The movements whilst recording are slow, I noticed your note in the code 
regarding "reduce empty meaningless records" but I wonder if it is 
feasible for anyone to generate recordings with that level of slowness?
If I interpreted correctly your intention, I wonder If it wouldn't be 
better to exclude those "empty meaningless records" at flush time or 
similar and still keep the fluidity of a normal app.
> B) generate test fixture
> freewrl -F -N fly2
> creates:
> /fixture/fly2.0001.bmp
> /fixture/fly2.log
> .
This does seem to play the recording well but ...
- The bmp file created is unreadable in my system, it looks like a file 
with a bunch of data and no header....
- I don't see any logfile being created.
> C) generate playback
> freewrl -P -N fly2
> creates:
> /playback/fly2.0001.bmp
> /playback/fly2.log
> .
Same thing here unreadable bmp and no logfile.
> D) run a perl script to compare fixture and playback files
I think this bit will be rather straightforward to achieve once 
everything is oiled enough.
Following on the initial code I have on github for the testing bit my 
plan is to have a script that drives FreeWRL and generates playbacks to 
then compare to the fixtures.