lunch a scenario without direct use of designer

[matthieuG]

After some exchange with administrators, I resume it for the community :

In case of a final user of openViBE (ex : a clinician), the best to resume openViBE execution is a shortcut, to be exactly as a standard software. To do this, a command file has to be produced and a shortcut to this file next.

How to build this command file?
First, create a file.bat (on windows). Next build a command with :
>>> test-designer [ switch ] [ scenario_name ]
>>> Providing scenario_name opens the scenario immediately
>>> Possible switches :
>>> -p --play : plays the opened scenario
>>> -pf --play-fast : plays fast forward the opened scenario
>>> example : test-designer.cmd -p ../scenarios/my-scenar.xml

a problem remains, the environment has to be initialized. So a good example for a command file created in openViBE source folder :

Code: Select all

@echo off
pushd ..\scripts
call win32-init_env_command.cmd
popd
cd bin
OpenViBE-designer-dynamic.exe -p 
..\share\openvibe-scenarios\neurofeedback\ICAneurofeedback_online\ICAneurofeedback_online.xml

But it does not work, it open the designer, without the scenario, without playing.

Another point, it could be nice to lunch a scenario without designer at all, only the interface generated.

[lbonnet]

But it does not work, it open the designer, without the scenario, without playing.

Sorry Matthieu, but the command line argument for the designer just works fine (fully tested on windows XP).
If you just copy-pasted the script as it is presented in your post, it won't work of course. The 2 arguments must be on the same line :

Code: Select all

@echo off
pushd ..\scripts
call win32-init_env_command.cmd
popd
cd bin
OpenViBE-designer-dynamic.exe -p ..\share\openvibe-scenarios\neurofeedback\ICAneurofeedback_online\ICAneurofeedback_online.xml

In your last post the scenario path was on the next line. In this case the program try to open a scenario named "-p".

As you probably noticed, this script is just a real simple modification of the basic script test-designer.cmd generated with the win32-build.cmd script, so no big deal at all.

NB1: this command line arguments will work only with the latest version of the designer, only available on the SVN. Next release will integrate this though.

NB2:as it is stated in the script, the actual syntax is:

Code: Select all

OpenViBE-designer-dynamic.exe [ switch ] [ scenario_name ]
Providing scenario_name opens the scenario immediatly
Possible switches :
      -p or --play       : plays the opened scenario
      -pf or --play-fast : plays fast forward the opened scenario
Example : OpenViBE-designer-dynamic.exe -p ../scenarios/my-scenario.xml

NB3:The designer must be called in an initialised environment, use win32-init_env_command.cmd prior to OpenViBE-designer-dynamic.exe for that purpose.

Another point, it could be nice to lunch a scenario without designer at all, only the interface generated.

We are currently having a lot of discussion about that feature and the best way to obtain it. The solution described in this topic is quiet simple, and fulfill our short-term needs. But something much more complex is in our minds

Laurent

[matthieuG]

OK, it works. I used a too old version of openvibe.

[matthieuG]

Is it also available with acquisition server? Can it be include in starting "service"?

[lbonnet]

The acquisition Server doesn't have such mecanism yet. But I will need it soon for a demonstrator.

I'll keep you posted !

Laurent