LE MCM: State or Option?

[Mattiewagg]

Just curious if, when you guys create MCMs, do you use the state system or the old option system?

I personally use the state system, but I've noticed a lot of mods with MCMs, even newer ones, don't use the state version.

Edited August 23, 2014 by Matthiaswagg

[jaxonz]

I'm with you. Using the state system makes it so much easier to organize your code.

 

I tried my first MCM using the older examples and soon became frustrated. I can't imagine using it for anything but the simplest of menus.

[Mattiewagg]

I'm with you. Using the state system makes it so much easier to organize your code.

 

I tried my first MCM using the older examples and soon became frustrated. I can't imagine using it for anything but the simplest of menus.

I used it for my very first before realizing the state option existed, and immediately switched to that. I imagine a lot of MCMs are so large people don't want to go through and make the change, but once you have it's so much quicker and cleaner.

[cdcooley]

The state system is much cleaner, but people tend to use the thing they learn first. Modders comfortable with the old, original method may not think it worth the time to learn a new way. Someone new may have found the old documentation or an old mod for reference and not realize there is a better way. (And some people might even prefer the original system for some reason.)

[Arthmoor]

Count me among those who didn't even know they'd added the state system, but after reading up on it, that's definitely a far cleaner and more organized way to do things.

[Mattiewagg]

Count me among those who didn't even know they'd added the state system, but after reading up on it, that's definitely a far cleaner and more organized way to do things.

Well you learn something new every day :smile:.

 

I was lucky enough to stumble upon it when I started with MCMs, so I used it from the start.

[schlangster]

Unfortunately, I only came up with the state-based approach after MCM had already been released. Otherwise, I would've made it the default, because it's clearly much nicer.

 

At that point I didn't want to push the new API too hard to avoid that people who already created their menus with the old API felt pressured to learn something new. Even if full backward compatibility is ensured, suddenly doing everything different would not have inspired confidence.

[Mattiewagg]

Unfortunately, I only came up with the state-based approach after MCM had already been released. Otherwise, I would've made it the default, because it's clearly much nicer.

 

At that point I didn't want to push the new API too hard to avoid that people who already created their menus with the old API felt pressured to learn something new. Even if full backward compatibility is ensured, suddenly doing everything different would not have inspired confidence.

Oh well. I'm glad it's an option at the very least. It is far more intuitive and clean.