I changed my mind. I am looking at Grid Ranges right now. It could be done tonight.

I changed my mind again. I'll post what I did on the current Ticket. This is not as much fun as I wanted it to be.

I was in two minds when I did that as to whether to make that kind of grid just completely different as a node handler.

The other thing that came up was this: now that grids are so MUCH more useful and neat and can hold all your data it becomes much nastier if you accidentally delete the wrong row or column so I was thinking about some sort of revert, cancel, undo... something like that. Right now at best you can exit OpenRPG without saving the tree and lose those mistaken changes to the grid along with all intentional changes that session.

I don't want to do this right now david. I am still reeling for your suggestion to reverse all of my changes and turn them into a plugin.

I think it is a kind gesture that you are willing to help .. but there is no room.

Alrighty.

I've re-written my stuff about three times
I think I am beginning to understand it better now!

Btw OpenRPG had some tests added to it. Did you ever look at that stuff? All this referencing code gets freaking complicated to check. It's all the recursive functions and so on. Ideally I'd like some tests for it. A suite where you can call a function that adds a set of nodes to a blank tree, then make a call to ParsePost probably and check the result is what you expect it to be; that the references were followed correctly etc. Then when you change the code you can run the test suite instead of manually trying to check you didn't break some old code.

Testing is never as exciting as adding new code of course :/