So I have been thinking about using slice collections (*) for menu layouts, and I am thinking that some kind of GridSlice would be useful.
The idea is that a gridslice is divided into even-sized rows and columns. Children of the grid automatically get moved to fill the grid squares. Suppose I want to reproduce the load game screen. I would create two slice collections, one according to the "Load Game Screen" template and one according to the "Load Game Info Panel" template. The Load Game Screen template would require a slices marked as "sl_load_new_button" "sl_load_exit_button" and "sl_load_grid" (not sure about the names, I am just making them up at the moment) The Load Game Info Panel would be fit into the grid slots in the other collection. it would have slots for the hero pictures, current map, current time, etc... ...actually, it would probably contain another grid for "Load Game Info Panel Hero Previews" which would be automatically filled from another slice collection that would allow walkabout, or battle or portrait sprites, and maybe names and stats (but to reproduce the current load screen it would just have the hero battle picture) Anyway, how do y'all like the idea of a slice grid? I think it would be a nice alternative to painstakingly arranging lots of same-sized container slices? (think of the master palette in the sprite editor That would be hell to convert to slices with no GridSlice) * I like saying "slice collection" a heck of a lot better than I like saying "screen layout". I am thinking of changing the name of the menu in custom... --- James Paige _______________________________________________ Ohrrpgce mailing list [email protected] http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
