+2009-06-20
+ * started with integration of native Supaplex engine, using source code
+ of Megaplex from Frank Schindler, based on original Supaplex engine
+
+2009-06-16
+ * version number set to 3.2.6.2
+
+2009-06-15
+ * version 3.2.6.1 released
+
+2009-05-31
+ * fixed bug with element_info[e].gfx_element not being initialized in
+ early game stage, causing native graphics in EMC level sets to be
+ mapped completely to EL_EMPTY (causing a blank screen when playing)
+ (this only happened when starting the program with an EMC set with
+ native graphics, but not when switching to such a set at runtime)
+
+2009-03-30
+ * deactivated blit-to-same-surface workaround again (see 2009-03-24)
+ and using self-compiled, patched SDL.dll that solves this problem
+ (interim solution until release of SDL 1.2.14 that should fix this)
+
+2009-03-26
+ * extended backwards compatibility mode to allow already fixed bug with
+ change actions (see "2008-02-05") for existing levels (especially the
+ Zelda and Zelda II levels and other cool stuff by Alan Bond like FMV)
+
+2009-03-24
+ * reactivated workaround to prevent program crashes due to blitting to
+ the same SDL surface that apparently only occurs on Windows systems
+ (this is no final solution; this problem needs further investigation)
+
+2008-11-05
+ * version number set to 3.2.6.1
+
+2008-11-04
+ * version 3.2.6.0 released
+
+2008-10-11
+ * fixed behaviour of player option "no centering when relocating" which
+ was incorrect when disabled and relocation target inside visible area
+ and "no scrolling when relocating" enabled at the same time
+
+2008-10-06
+ * fixed problems with re-mapping players on playfield to input devices:
+ previously, players found on the level playfield were changed to the
+ players connected to input devices (for example, player 3 in the level
+ was changed to player 1 (using artwork of player 3, to be able to use
+ a player with a different color)); this had the disadvantage that CE
+ conditions using player elements did not work (because the players in
+ the level definition are different to those effectively used in-game);
+ the new system uses the same player elements as defined in the level
+ playfield and re-maps the input devices of connected players to the
+ corresponding player elements when playing the level (in the above
+ example, player 3 now really exists in the game and is moved using the
+ events from input device 1); level tapes still store the events from
+ input devices 1 to 4, which are then re-mapped to players accordingly
+ when re-playing the tape (just as it is done when playing the level)
+
2008-09-29
* fixed bug with player relocation while the player switches an element
projects / rocksndiamonds.git / blobdiff