[screenweaver] Fatal Exception when building application
Edwin van Rijkom
swos at vanrijkom.org
Mon Aug 29 07:29:11 PDT 2005
Romain ECARNOT wrote:
> I need to recompil the swf all the times and rebuild sw application
> (.exe) to show result. ;)
There's a nice way to circumvent the Screenweaver re-building if you've
installed the latest patch:
Create your project with the Screenweaver GUI only once. The output
should be a stand-alone Screenweaver projector.
Create a batch file (or use Start menu's 'Run' ) to launch the created
projector with the folowing command line arguments:
yourprojector.exe /sw3debug "pathToASAPI.swf"
"pathToProjectSettings.sws" "pathToUserMovie1.swf"
More user movies can optionally be added to the commandline. Internally
the the movies will be given the Id's "Movie 1", "Movie 2" ... "Movie
n". You can use environment variables "%APPDATA%", "%TEMP%" in your paths.
The projector will now launch with the settings specified in the .sws
path you specified. All settings are applied, except for the files you
packed with the project - those are replaced by what you specified on
the command line.
If you didn't check out the sources, you'll need to download the AS API
file:
https://secure.sourcesecure.co.uk/trac/osflash/screenweaver/browser/three/trunk/src/actionscript%20api/api.swf.
Needless to say, this is now also provides an excelent way to work &
test the API without having to recompile the C++ sources.
When working on your movies in Flash, al you need to do to test them
with Screenweaver is invoking the batch file. Be aware that when loading
external movies with Flash's LoadMovie, the player will be looking for
them relative to the projectors path - not relative to the location of
your movie.
Cheers,
Edwin
More information about the screenweaver
mailing list