On Thu, Sep 21, 2017 at 19:56:30 +0100, D Haley wrote: > It looks like the QT UI does not match what happens internally in Octave > if the line is absent from the file. > > If the line "allow_web_connection=true" is present, then the web > connection proceeds, and the network tab in settings reflects the setting. > > If the line "allow_web_connection=false" is present, then the web > connection does not occur, and the network tab in settings reflects the > setting. > > However, if the line is entirely absent, then the connection is > established, however *the UI does not show this*. The item in the menu > for the network connection is unchecked.
Your analysis seems correct to me. Is it possible the qt-settings file is created by something other than Octave on your system? Not that this is a bad thing, but it's also not entirely well-supported, as we've now seen. The 'news/allow_web_connection' setting has been present and has been checked since the GUI was first introduced in 3.8.0, so it is not likely that this was missing due to an upgrade from a previous version. It's more likely that the qt-settings file was modified outside of Octave or was created or pre-seeded by some other tool. Do you think there is any remaining issue here, or do you consider this resolved by fixing the configuration file on your end? Or is the only issue here that the settings dialog implies that the missing value defaults to 'false', while the actual behavior is to interpret a missing value as 'true'? -- mike
signature.asc
Description: PGP signature