improvement idea for v4

[MattB]

Much as I enjoy meeting fellow 'banders I think it will be tricky for us since we live in different countries.

Well Magnate, I live just down the road from you and you've never invited me for tea! Hrrmph.

[Derakon]

Well Magnate, I live just down the road from you and you've never invited me for tea! Hrrmph.

One might imagine Magnate feels the same way about you! Who shall invite whom first?

[Magnate]

One might imagine Magnate feels the same way about you! Who shall invite whom first?

I was just going to say "well join the devteam then!" - but then I realised that my attendance for the past two years has been so poor that he might well have done and I'd have missed it.

@MattB - mi casa su casa - I look forward to meeting you soon!

[Timo Pietilä]

I couldn't agree more.

That kind of double-negative is easier to understand than some policies where you enable something to disable something. Now disabling that policy would enable that something. Makes really easy to make mistakes when you are tired and suffer from caffeine deprivation.

Like this:

Compare yourself:
Disable Stacking Objects on the floor : Disabled
Disable generating connected stairs : Disabled
Disable showing Level Feelings : Disabled

[Tibarius]

re: disableing

I am sorry, i do not understand you Timo.

Do you say it is easier to read:
Disable connected stairs: Disabled

instead of:
Generate connected stairs: No

???

[Timo Pietilä]

I am sorry, i do not understand you Timo.

Do you say it is easier to read:
Disable connected stairs: Disabled

instead of:
Generate connected stairs: No

???

Opposite of that. And BTW you just made the error I was talking about:

Disable connected stairs: Disabled
equals
Generate connected stairs: yes

[Tibarius]

yeah

Yeah - i was not totally accurate about the example. because i had the Feeling i haven't understood what you were saying. I guess we agree that the 2nd type of naming and using Options is the easier to understand way.