dontconnect not honoured

[sigoa]

on a pristine install, if you modify PORTABLE mode and / or change NETWORK settings - say SOCKS5 settings back and forth - or such - then pyBM (run from current v0.6 py sources in Linux) will connect even though initially DONTCONNECT is set in the KEYS.DAT file. This may be surprising or not desirable behaviour.

so if you really want DONTCONNECT, you have to pull the network cable, thus air-gapping the machine.

Peter says, he "cannot reproduce" it, so make of it what you want. 👍

[PeterSurda]

Ok I'll look at it, maybe it's the portable mode that is causing this.

[g1itch]

You did not bother to explain the issue. For example:

1. select File -> Go offline
2. close PyBitmessage
3. check "Work offline" in ConnectDialog upon next start
4. open and close settingsDialog
5. now PyBitmessage connects to the network although it should not

[ffox8]

can be tested using #1178
and 3 options

[PeterSurda]

I think that people expect PyBM to remain offline after closing the settings dialog. I think that maybe after closing settings, the three-choice dialog should show up again. That appears to be more understandable for a beginner.

[sigoa]

"let me configure..." does not imply that BM goes online after I am done configuring.

"let me configure..." option needs to be stated unambiguously, i.e.:

"let me configure and stay the heck OFFLINE"

[dimyme]

does not look 100% OK to me either. the menu option wording ("conn./disconn netwk") is inconsistent initially.