I assume that this is your own flash object so you can set the parameters. You need to make it look for the file and I would think using a relative path would be the best option.
For both the development and published versions of a module the file structures are very similar.
I'd put the both the files in their own sub folder of the folder named "1".
Courselab should add this properly to it's manifest.xml so will reference it OK.
Post publishing I'd check to make sure the folder exists, if not just drop a copy of your folder and contents into the same level. You should also check the runtime.xml to make sure that the module is referencing the location of the flash object correctly. This will be a relative (to runtime.xml) link
This should work.
Courselab won't track the location of the file the flash object refers to as it's not under it's control and essentially unknown. If you use the option to clean out excess files (Module -> Delete Unused Files) it will possibly remove your files and folders.
I assume that this is your own flash object so you can set the parameters. You need to make it look for the file and I would think using a relative path would be the best option.
For both the development and published versions of a module the file structures are very similar.
I'd put the both the files in their own sub folder of the folder named "1".
Courselab should add this properly to it's manifest.xml so will reference it OK.
Post publishing I'd check to make sure the folder exists, if not just drop a copy of your folder and contents into the same level. You should also check the runtime.xml to make sure that the module is referencing the location of the flash object correctly. This will be a relative (to runtime.xml) link
This should work.
Courselab won't track the location of the file the flash object refers to as it's not under it's control and essentially unknown. If you use the option to clean out excess files (Module -> Delete Unused Files) it will possibly remove your files and folders.
