If you are developing on a Mac a way round this problem is to make a disk image using Disk Tools (probably the sensible idea is to make it the same size as the media you intend to burn it to: DVD/CD) - make sure the image is Read/Write: mount it on the desktop and do all your development INSIDE IT.
This means that all your files paths will point inside the disk - so where-ever the disk goes the paths SHOULD (Hm ?) stay the same and behave themselves. In this way you don't have to embed all your media - and find that your target computers grind to a halt as they don't have the RAM to cope with loading EVERYTHING (!!!!!!) at once. Another way to cope with this is to load media into individual substacks which end up in a 'data' file when you build your standalone (again - best to develop inside a disk image) and can be loaded and unloaded from RAM as required. sincerely, Richmond __________________________________________________ See Mathewson's software at: http://members.maclaunch.com/richmond/default.html _______________________________________ --------------------------------------------------------------- The Think Different Store http://www.thinkdifferentstore.com/ For All Your Mac Gear --------------------------------------------------------------- _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
