I have a course made up of 6 sections. Each section (aka file) includes several different scenes. I would like to publish my course to a CD and have a Main Menu that users will see that they can use to access each section (file) of the course.
I do not want to combine the whole course into one gigantic file. First of all, each file is big enough as they stand now, plus I like that each section of the course has it's own menu.
So, does anyone know if I can create a MENU that has buttons that "jump" out and run each file?
Having a similar issue with size of project and have course I can separate. They will not need to communicate with each other so a simple menu that would launch each file would be great. These will be on a flash drive not a CD but do not see how that would matter. The issue I am having is I cannot seem to get the individual storyline files to run from the one slide menu story. Can you explain working with the URL structure a bit to make sure that the buttons are able to find the other launch files??
I cannot seem to get this method to execute, I am publishing for CD but need to distribute on a usb drive. I have the menu button set to Jump to URL/file and asking to go to E:\\ RespProtectNew - Storyline output\\Launch_Story.exe. when user clicks menu button. this is not working and ideas?
I think the challenge is the URL system that you're using. If you tell SL to look to a particular drive (A:, B:, C:, etc.) you'll run into difficulties. The reason is that once someone sticks a USB drive into their machine, it may not be assigned the same letter.
I'd do this...
1. Publish out your courses that you're linking to.
2. Make note of the folder name and the launcher file name (be it an .exe or an .html). So in the following image, I name the course folder (course01) and make note of the "Launch_Story1.exe" name (assuming I want to use the .exe to launch the course).
3. Now, in your Menu storyline project, when you link to the course, don't use any drive letters. Rather, establish the URL link with just the folder name and launcher file name.
4. Publish out your menu course.
5. Place the courses that the menu course will launch inside the published menu project folder.
6. Drop the menu project folder (that now contains the courses) onto your USB.
Mike,
Thanks for the reply but still get an error message. Followed your instructions to the letter. Not sure why I cannot get this to work, it should not be this difficult.
OK I got it, now how do we stop this from coming up and making people nervous, because the second one that comes up says the certificate from the content cannot be verified.
40 Replies
Should have been a little more clear with my last msg. JavaScript trigger:
window.location('../another_module/story_html5.html')
Having a similar issue with size of project and have course I can separate. They will not need to communicate with each other so a simple menu that would launch each file would be great. These will be on a flash drive not a CD but do not see how that would matter. The issue I am having is I cannot seem to get the individual storyline files to run from the one slide menu story. Can you explain working with the URL structure a bit to make sure that the buttons are able to find the other launch files??
I cannot seem to get this method to execute, I am publishing for CD but need to distribute on a usb drive. I have the menu button set to Jump to URL/file and asking to go to E:\\ RespProtectNew - Storyline output\\Launch_Story.exe. when user clicks menu button. this is not working and ideas?
Hi Tom! This thread is a bit dated, but hopefully someone in the community will be able to pop in and assist you with this request.
Hi Tom,
I think the challenge is the URL system that you're using. If you tell SL to look to a particular drive (A:, B:, C:, etc.) you'll run into difficulties. The reason is that once someone sticks a USB drive into their machine, it may not be assigned the same letter.
I'd do this...
1. Publish out your courses that you're linking to.
2. Make note of the folder name and the launcher file name (be it an .exe or an .html). So in the following image, I name the course folder (course01) and make note of the "Launch_Story1.exe" name (assuming I want to use the .exe to launch the course).
3. Now, in your Menu storyline project, when you link to the course, don't use any drive letters. Rather, establish the URL link with just the folder name and launcher file name.
4. Publish out your menu course.
5. Place the courses that the menu course will launch inside the published menu project folder.
6. Drop the menu project folder (that now contains the courses) onto your USB.
I just tested locally and it seems to work fine.
I hope this helps!
Mike
Mike,
Thanks for the reply but still get an error message. Followed your instructions to the letter. Not sure why I cannot get this to work, it should not be this difficult.
Tom,
Can you post screenshots of your trigger/links in Sl2 as well as your file structure (both inside the menu folder and inside the course folder).
Thanks for taking the time to look this over, I know the answer is probably right in front of me, just can’t see it
Me either. Did you post pics? ;)
Yes they were attached to the last email?
They didn't come through. You may need to post from the web.
Also, just as a heads up, your last post has all of your email footer info (address, phone, etc.).
Mike
I think they should have been uploaded and hopefully I was able to edit that post?
Yeah, I'm not seeing anything odd there.
Try this, here's the output that's running locally on my machine. Unzip it and see what happens on your end when you run it from a USB.
Mike
OK I got it, now how do we stop this from coming up and making people nervous, because the second one that comes up says the certificate from the content cannot be verified.
That one I don't have an answer for as I believe it's the local security settings (browser?) that cause that error.
Mike
PS. Out of curiosity, what was the change you needed to make in your file structure to get it to launch?
This discussion is closed. You can start a new discussion or contact Articulate Support.