Browser detection is incomplete

[chennecke]

NewView seems to detect the default browser by querying the standard settings for URL objects. This works for the browser executable but additional command line options that are specified in the "Parameter" (for a German eCS, is that "Options" in English?) entry field are ignored.

Working around this probem by using a CMD file is impossible since NewView is incapable of starting the CMD file. All I get is a black screen for a short while and then it switches back to the WPS and nothing happens.

[RBRi]

At the moment NewView uses the user ini entry named WPURLDEFAULTSETTINGS. DefaultBrowserExe and DefaultWorkingDir are used to start the browser. If this key is not available, then it tries to find explorer.exe in the path.

I think, you are right, that this is not the most flexible solution. What about adding a new page to the options where you can define the browser and only using the existing mechanism to determine the initial values for this?

What do you think?

[chennecke]

You could of course provide a way to override it, but the default should work correctly.

I took a look at my INI file. Under WPURLDEFAULTSETTINGS, there is a key called "DefaultParameters". It contains the parameters entered in the URL object's Parameter entry field. I'd prefer this to be respected if the user does not explicitely choose to override it.

Thanks for looking into this.

[anonymous]

OK i have added support for the DefaultParameters key. I think, there is no need for a separate configuration page in NewView. There are so many way's to configure OS/2-WSP that i think we need nothing more.

Fix will be part of the 2.19 release (released hopefully this weekend :-).