+2007-10-29
+ * fixed bug with reference elements used as trigger elements on custom
+ element change pages not being recognized
+ * fixed bug with reference elements not being removed from the playfield
+
+2007-10-23
+ * added command line function to write level sketch images to directory
+
+2007-10-20
+ * merged override and auto-override options into new override options
+ with a new data type than can take the values "no", "yes" and "auto"
+
+2007-10-18
+ * fixed growing steel wall to also leave behind steel wall instead of
+ normal, destructible wall
+ * fixed handling of rocks falling through stacks of quicksand with
+ different speed (before, the rocks just got stuck in the quicksand)
+
+2007-10-09
+ * fixed nasty bug with auto-override and normal override not working on
+ program startup (especially when current level set has custom artwork)
+
+2007-10-05
+ * version 3.2.5 released as special edition "R'n'D jue"
+
+2007-10-05
+ * fixed X11 crash bug when blitting masked title screens over background
+
+2007-10-04
+ * changed build system to support special editions (like "R'n'D jue")
+ * added (hardcoded) loading graphics for "R'n'D jue" special edition
+ * fixed X11 crash bug when scaling images with width/height less than 32
+
+2007-09-27
+ * added "background.PLAYING" (only visible as two-pixel border in game)
+ * added default level set for first start of special R'n'D version
+ * changed door animations for editor always behaving like "quick doors"
+
+2007-09-26
+ * added new custom artwork setup option "auto-override non-CE sets" for
+ automatic artwork override that is only used for level sets without
+ custom element artwork (as it does not make much sense to override
+ any artwork that redefines custom element artwork for sets using CEs)
+ * fixed default artwork for "special" R'n'D versions always using the
+ "classic" artwork as the base if base artwork is not explicitly
+ defined in "levelinfo.conf", regardless of different default artwork
+ used by the special R'n'D version -- this is needed because any such
+ custom artwork is designed using the "classic" artwork definitions as
+ the base (including menu definitions and screen positions etc., which
+ would otherwise be taken from the different special default artwork)
+