- also allow users to see, if the default proxy (-proxy) is used for IPv6 and Onion
- based on #4871 (formerly #2575)

Looks good.
As discussed in #2575 I'd like to simplify this to:
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/p4587_776d006492d75c94cbff1edf7fae760f0a95ebcf/ for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
Needs rebase or close due inactivity.
Sorry. Your right. It's on top of #4871
Rebased and passing travis :).
@laanwj @jonasschnelli Mind taking a closer look now?
@jonasschnelli @laanwj This should be ready.
Gave it a short test.
Why can't i unselect/select the IPv4/IPv6/Tor checkboxes (i didn't start reading why in the PRs description because IMO this must be clear within the app). If it's just as a visual prove what networks are supported by the proxy, it should not use read-only checkboxes.
The new height of the settings window does somehow look strange on the other tabs. Auto-Resizing like this (https://vid.me/F53C) would be a better approach (check: http://stackoverflow.com/questions/11441809/resize-window-using-qpropertyanimation).
IMO the autoresizing would be nice but should not hold this PR back.
<img width="714" alt="bildschirmfoto 2015-07-21 um 21 28 22" src="https://cloud.githubusercontent.com/assets/178464/8810518/c688a5aa-2fef-11e5-923d-3b2ceb3aff35.png">
@jonasschnelli I choose the read-only checkbox approach as that seemed easy to do. What elemet do you suggest? As you discovered the state is not changable via the boxes, they just give information.
The resize issue is a different one and as far as I understand the link you gave me, this is just for getting a nice and smooth animation, but I don't even know how to resize a window so that the contents and size are matching and that it looks good ;). IMHO our client suffers from these issue nearly everywhere.
ut ACK
Is this ready for merging? Blockers appear to be resolved.
Readonly-Checkboxes as visual indicator for a available option (but while actually supporting no interaction) should be avoided. But i can address this in another upcoming PR after merging.
I would recommend to use the checkmark icon instead (https://github.com/bitcoin/bitcoin/blob/master/src/qt/res/icons/transaction2.png).
@jonasschnelli I'd love to get this in or you could just add a commit to it. But I'd love to move forward.
Doesn't compile at the moment because of the recent "emit" changes (https://github.com/bitcoin/bitcoin/pull/6433).
- also allow users to see, if the default proxy (-proxy) is used for
reaching peers via IPv6 or Tor
@jonasschnelli fixed the emit problem.
<img width="707" alt="bildschirmfoto 2015-07-24 um 12 43 12" src="https://cloud.githubusercontent.com/assets/178464/8872987/3fdcaee2-3202-11e5-9e75-8774bc27f957.png">
<img width="295" alt="bildschirmfoto 2015-07-24 um 12 55 46" src="https://cloud.githubusercontent.com/assets/178464/8873081/5456c3f2-3203-11e5-9f2e-a07531cacd12.png">
I think this looks better. Commit: https://github.com/jonasschnelli/bitcoin/commit/3ae243422abfbdaa8c5a56ebdf86d4fedeaa467c
@jonasschhnelli I like what you're trying to do, but I'm not sure it's better:
Going to merge this as-is for now. You can improve it later.
ACK.