I think that the toolset/script engine would benefit from the following functions (based on the module object):
object getNextArea(); /* would return NULL if there are no nextAreas */
object getPreviousArea(); /* NULL if no previous Area */
object getFirstArea();
object getLastArea();
int getAreaCount();
All of these would return an area object except the areaCount of course.
The reason I think we need something like that is because of area cleaner scripts. It would be a lot easier if we had an easy way to cycle through all of the areas. It is true that we can keep our own list of areas and write our own function to loop through them. But... with such an obvious benefit to the community, why not make it automatic? The module must have a build in list of valid area objects already, and the area/object functions are already in place to retrieve names and such. We just don't have an easy way to obtain all of the valid module area objects (to my knowledge).
A module event could cycle through each area and do a cleaner script against it. This would save us form having each area trigger a cleaner event.
10 - A Masterpiece, Genuinely Groundbreaking 9 - Outstanding, a Must Have 8 - Excellent, Recommended to Anyone 7 - Very Good, Deserves a Look 6 - Good, Qualified Recommendation 5 - Fair, Solid yet Unremarkable 4 - Some Merit, Requires Improvements 3 - Poor Execution, Potential Unrealized 2 - Very Little Appeal 1 - Not Recommended to Anyone
Site
at 2006-12-16 06:12:53
