🚀 go-pugleaf

I think I know why the Parameters argument doesn't help.

See thisn MSKB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;224816
Excerpt:
ShellExecute parses the string that is passed to it so that ShellExecute can extract 
either a protocol specifier or an extension. Next, ShellExecute looks in the registry 
and then uses either the protocol specifier or the extension to determine which 
application to start. If you pass http://www.microsoft.com to ShellExecute, 
ShellExecute recognizes the http://  sub-string as a protocol, which causes 
ShellExecute to view HKEY_CLASSES_ROOT\http\shell\open for information about how to 
run. If you pass myfile.htm to ShellExecute, ShellExecute recognizes the ".htm" 
sub-string as an extension. This causes ShellExecute to view HKEY_CLASSES_ROOT\.htm, 
which leads to HKEY_CLASSES_ROOT\htmlfile\shell\open.


Well, I'm using "file://" rather than "http://" and I'm not ending the string with 
".htm" and so the two ways it uses to choose the 
HKEY_CLASSES_ROOT\htmlfile\shell\open are both not working.

Anyone have any ideas on how to open a local file in a browser when the URL includes 
a #OffsetLink into the HTML page?


Bob Gonder wrote:

> Have you tried using the parameters value?
>  AnsiString UrlStr=
> 	"file://"+ExtractFilePath(Application->ExeName)+"myfile.htm";
>  AnsiString Param = UrlStr+"#HotKeys";
> 
> ShellExecute(NULL,"open",UrlStr.c_str(),Param.c_str(),0,SW_SHOWDEFAULT);
> 
> Don't forget to put extra quotes around the path to account for spaces
> and other nasties that are allowed in paths, but look a lot like
> zwhitespace.
> 
> Param = "\""+Param+"\"";
> 
>