sweet stuff dude
I peeked at the options stuff and I will mess around with it when I get some time
I always like building gui stuff but it's so damn time consuming
are you unemployed?
School
and work.
Making the GUIs is actually pretty easy since you can just exec gui.cs files to create objects. Really, you could just edit Options.gui.cs and make a menu item in 30 seconds. I just wanted to see how I could do it outside of the base folder. I think my method for importing the objects is piss poor though. There must be a better way. If I had the time I'd look at newOpts and figure out what's going on in there, but I really don't know enough.
Since the code is pretty messy, I'll explain what's going on. Basically, the following is happening:
1] Executing a gui.cs file to create the page and menu item for "Extras." I call this the 'set'.
2] Recursively finding where those 'set' objects go in the GUI tree, then adding them to the appropriate node. This is done by supplying the name of a sibling node of the same level and getting the parent node's Id.
3] Each script then has its own gui.cs that is executed, which builds objects at the top level, and then there is some code in each script file that adds those objects to the "Extras" 'set'
The overall logic seems to work, but my implementation is pretty bad. Ideally, I'd like to find a better way of sticking the 'set' pages into the GUI tree. And I'm not really sure if I am extending the right functions. I had to stick a boolean variable into the script just to make sure it doesn't keep trying to add objects to the GUI once the Options page has been loaded once.
There are tons of problems, it's no where near functional enough to use.
Maybe if I get some time I can figure out how to clean it up, but I figured you guys would be more capable.