🚀 go-pugleaf

Randall Parker wrote:

>1) Can I assume that any path passed to a browser will be interpreted as being a 
>relative path to the current exe? I'm guessing the answer is NO. So how to find out 
>the path of the exe?

See GetModuleFileName()
Then parse out the exe name, leaving the path.

>2) Is there a syntax for a local file URL that all browsers recognize? I see that IE 
>doesn't do file:/// for files you open locally but Mozilla does use that syntax.

I use ShellExecuteEx() using "open" and the full path, nothing fancy.

>4) How to convert the local path to URL format with the backslashes converted to 
>forward slashes? Is there a routine in a BCB or OS lib that will do this?

Don't think that's needed, but it's easy enough to roll your own.

>5) Is it necessary to do double quoting escapes for paths that have spaces in dir names?

Depends on how you are launching it.

	SHELLEXECUTEINFO si={sizeof(SHELLEXECUTEINFO),0};
	si.lpVerb = "open"; 
	si.lpFile = fullfilename; 
	si.lpDirectory = dir;
	si.nShow = SW_SHOWNORMAL;
	lstrcat(lstrcpy( fullfilename, dir),"\\manual.htm");
	ShellExecuteEx(&si);

>6) Is there a way to tell the browser to open a new instance/window/tab rather than 
>replace the current page of the browser with the new page?

Perhaps CreateProcess()?  In which instance, you would probably want
to add quotes to your path.