Windows freenet systray app has been updated to periodically probe the Web
Interface port on startup and only enable certain behaviour if a connection
can be made. Specifically the following *won't work* now unless/until a
connection can be made to mainport:
1. Specifying -open on command line to freenet.exe to open Web Interface
2. Double-clicking the systray icon to open Web Interface
3. Right-clicking the systray icon to open Web Interface ("Open Gateway"
will now appear greyed-out until a connection can be made)
4. Launching another copy of Freenet (which would ordinarily automatically
open the Web Interface for you, as a shortcut).
5. Tooltip reporting "Freenet Is Running" (tooltip will now continue to
report "Freenet Is Starting" until a connection to mainport can be made)
6. Hops icon changing in the systray (icon will remain as a ghosted-out
progressive animation until a connection is made)
This prevents uninitiated users trying to use freenet before it is 'ready'
(and resulting in a "This page cannot be found" in their browser window)
thereby quashing a common Windows freenet complaint.
Note the above features are *not* delayed-startup, simply disabled (so e.g.
if you doubleclick hops while it is still saying "Freenet Is Starting" it
*won't* then automatically launch a Web Interface when it detects mainport
is running). However "freenet.exe -open" *IS* delayed-startup now so you
can specify the -open switch in the shortcut to Freenet to cause it to load
a Web Interface page on startup after it's detected.
Source in CVS and upxd freenet.exe in snapshots for automatic
webinstalls/upgrades.
d
_______________________________________________
devl mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
