I am yet to change the other one, will add that commit here too!

Took liberty of making a more descriptive title. ...

updated with changes

@QuLogic Did you mean something like this?
I thought sequential viewing might be better, but yeah this also makes sense!

Yes, that is fine. You have some flake8 errors though:

./examples/event_handling/pick_event_demo.py:106:1: W293 blank line contains whitespace
./examples/event_handling/pick_event_demo.py:148:1: W293 blank line contains whitespace
./examples/event_handling/pick_event_demo.py:163:1: W293 blank line contains whitespace
./examples/event_handling/pick_event_demo.py:164:18: W291 trailing whitespace
./examples/event_handling/pick_event_demo.py:182:1: W293 blank line contains whitespace
1     W291 trailing whitespace
4     W293 blank line contains whitespace

@meeseeksdev backport to v3.0.x

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

$ git checkout v3.0.x
$ git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

$ git cherry-pick -m1 02abf442ca5f0109fcbbd9e779f0f7bfe2348f24

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

$ git commit -am 'Backport PR #12222: Remove extraneous if 1 statements in demo_axisline_style.py'

4. Push to a named branch :

git push YOURFORK v3.0.x:auto-backport-of-pr-12222-on-v3.0.x

5. Create a PR against branch v3.0.x, I would have named this PR:

"Backport PR #12222 on branch v3.0.x"

And apply the correct labels and milestones.

Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon!

If these instruction are inaccurate, feel free to suggest an improvement.

Meh, I don't see the need.