Hi, Matt.
> > Well, but - should not this be automaticaly detected by Voyager, like
> > what IBrowse does? Eg. if bdsocket.library is not yet found or cannot be
> > opened, try OFFline browsing.
> > If bdsocket.library is "into place", then ONline browsing have to be used.
> > A good and relatively simple suggestion, nope?
> Also a relatively stupid one, since Voyager already DOES do this -
> if you check your Settings../General Settings../Network prefs page it
> is set between "TCP/IP stack" (which includes checks for Miami and
> Genesis using their own APIs - this is one of the functions of that
> mysterious vapor_toolkit.library you have in LIBS:) and "Manual"
> (which uses the Offline Browsing check gadget in the Settings.. rmb
> menu, and nothing else).
Yenah, thats true, but when i select the detection TCP/IP stack, then
Voyager do not close own screen on exit. Therefore i must have this
option disabled.
> If he has it set to Manual, and the Offline Browsing switch is set, V
> will never access the network and instead look to the cache for every
> file it needs. This is his problem.
Yes, but things wont work - V do not close the own opened MUI screen,
so, this is not a solution...
> Next time you feel the need to make a suggestion, make sure it isn't
> right in front of your face and hasn't been implemented since Voyager
> 3.0 ;)
> Matt
Yea, you are right, but i reporting that enabling automatic detection of TCP/IP stack
cause problem... :-(
Trodas
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
