Saturday, March 27, 2010

Project Preferences-close project at end

I have set up my quiz under ''Project Preferences'' to close
when the project ends. however, when the published project ends,
the browser is still open. I have to manually close it. Any
thoughts?Project Preferences-close project at end
Hi there



Whether the browser will actually close or not depends on a
few different factors.



* Browser make and model

* How exactly your page was opened



If you simply linked from perhaps a web page displaying in
the browser to your Captivate and the Captivate replaced the web
page, odds are that the browser will refuse to close. This is by
design. Otherwise, you could saw off the branch you are sitting on
(so to speak). But if you linked to your Captivate by having the
browser spawn a new window, it should close without issue.



Just Google a bit for something like ''JavaScript Close
Window'' and you will undoubtedly find hundreds (if not, thousands)
of hits that discuss this very situation.



Cheers... Rick
Project Preferences-close project at end
A third issue may be how you're accessing the published
files.



Since web pages are meant to be run from a web server, you
get all kinds of unpredictable results if running a file locally.
You know you're running a file locally if the URL in the browser's
Address bar starts with something other than
http:// or https:// (for example, file:// or
C:\).



There's lots of security restrictions when running files
locally that make it seem like files are ''broken'', when in fact
they are just prevented from working by the security features of
the browser and/or Flash Player.



The easiest way to around such restrictions is to always test
your files from a web server. Otherwise, you've got to monkey with
your browser and/or Flash Player settings, which doesn't always
seem to work. Do a search in these forums and you'll see a number
of posts that discuss how to modify your settings to try to get
local access working.
Thanks for the advice. It is much appreciated!

No comments:

Post a Comment