Better MapGrh-bound wall handling in maps

[GoogleCodeExporter]

Right now, the walls added to a map automatically from the walls bound to a 
MapGrh is pretty poor. In the file, they look like any other wall, so a 
reverse-lookup has to be done to guess which walls were from MapGrhs. A better 
approach would probably be to just add the GrhIndex into the wall to represent 
the MapGrh it came from, and store that in the file. Though to avoid overhead, 
I'll want to avoid creating the class containing this value unless in the 
editor.

Original issue reported on code.google.com by Spodiii on 8 Oct 2010 at 3:50

[GoogleCodeExporter]

The more I map, the more I realize that I don't even really want the 
MapGrh-bound walls. So I'm just going to leave it as-is. Even if its ugly, it 
works.

Original comment by Spodiii on 14 Oct 2010 at 12:49

• Changed state: WontFix