# HG changeset patch
# User Paul Boddie <paul@boddie.org.uk>
# Date 1359567247 -3600
# Node ID e90a2aa837d2d217d4b87bec1e646033a7253093
# Parent  7ac1f697367cc2ee90573eb95f2b778c93595c0e
Added information about event page regions.

diff -r 7ac1f697367c -r e90a2aa837d2 pages/HelpOnEventAggregator
--- a/pages/HelpOnEventAggregator	Wed Jan 30 18:17:17 2013 +0100
+++ b/pages/HelpOnEventAggregator	Wed Jan 30 18:34:07 2013 +0100
@@ -116,6 +116,28 @@
 
 Be careful ''not'' to start a distinct event with a property that was ''not'' recorded for the previous event: the result will be the property being added to the previous event, even if the property appears adjacent to the rest of the new event definition.
 
+=== Using Event Regions to List Events ===
+
+To be certain of events being defined individually, it is possible to use event regions rather than rely on !EventAggregator to figure out where events begin and end in the page. For example:
+
+{{{{
+{{{#!event
+ Start:: Monday 1st February 2010 (2010-02-01)
+ End:: Monday 1st February 2010 (2010-02-01)
+ Summary:: MoinMoin User Group Meeting
+}}}
+
+Previous meetings:
+
+{{{#!event
+ Start:: Monday 4th January 2010 (2010-01-04)
+ End:: Monday 4th January 2010 (2010-01-04)
+ Summary:: MoinMoin User Group Meeting
+}}}
+}}}}
+
+By using event regions explicitly, it becomes possible for enhanced formatting and manipulation of the event data to be supported by !EventAggregator and other !MoinMoin extensions.
+
 <<Anchor(TimeProblems)>>
 === Occasional Problems with Times ===