Difference between revisions of "Testing your application"
From NAMIC Wiki
Line 3: | Line 3: | ||
== Testing procedure == | == Testing procedure == | ||
− | * | + | * Download the config files in the previous page: '''Send.txt''' and '''Receive.txt''' (you can rename them as xml files but it's not necessary) |
* On your computer, create two shell terminal windows | * On your computer, create two shell terminal windows | ||
* In both terminal, change directory ('''cd''') to your NaviTrack-build directory | * In both terminal, change directory ('''cd''') to your NaviTrack-build directory |
Revision as of 18:28, 15 May 2007
Home < Testing your applicationHere comes the point you want to test how your application works. At this moment, we're not going to use any real tracking device; instead, we will use ConsoleSource, a built-in module in NaviTrack, to simulate the generation of tracking data.
Testing procedure
- Download the config files in the previous page: Send.txt and Receive.txt (you can rename them as xml files but it's not necessary)
- On your computer, create two shell terminal windows
- In both terminal, change directory (cd) to your NaviTrack-build directory
- In one terminal, run this:
./myapp send.xml and then press 1
- In the other terminal, run this command:
./myapp receive.xml and then press 1
- Have the input focus for the terminal running the sending process. Press some keys on the keyboard (see next section) to generate simulated tracking data.
- You should see the data update in the other terminal (the receiving side)
- All received data will be also saved into a file named file-out.txt in the same directory where you run your application
How to use ConsoleSource
On page 33 of this pdf file:
http://studierstube.icg.tu-graz.ac.at/opentracker/html/howto_opentracker.pdf
you will find all possible functions and their default keys on your keyboard for using ConsoleSource.