aboutsummaryrefslogtreecommitdiff
path: root/engines/agi
diff options
context:
space:
mode:
authorMartin Kiewitz2016-02-14 02:06:50 +0100
committerMartin Kiewitz2016-02-14 02:06:50 +0100
commite24fbf7d6e422ab188910e9a5f8c7fd5c190ac35 (patch)
tree3b2168261bbd53705b3e83486b1579510dbce650 /engines/agi
parent9a9ddc777e2fe1fe17db737915d0e1abd166cf86 (diff)
downloadscummvm-rg350-e24fbf7d6e422ab188910e9a5f8c7fd5c190ac35.tar.gz
scummvm-rg350-e24fbf7d6e422ab188910e9a5f8c7fd5c190ac35.tar.bz2
scummvm-rg350-e24fbf7d6e422ab188910e9a5f8c7fd5c190ac35.zip
AGI: Fix another comment about dynamic priority table
Available also in 2.425, then removed until 2.936, yada yada. priorityToY-Glitch is definitely present in 2.425 as well.
Diffstat (limited to 'engines/agi')
-rw-r--r--engines/agi/graphics.cpp5
1 files changed, 4 insertions, 1 deletions
diff --git a/engines/agi/graphics.cpp b/engines/agi/graphics.cpp
index e1ae62ef7a..6f4b272e2b 100644
--- a/engines/agi/graphics.cpp
+++ b/engines/agi/graphics.cpp
@@ -821,7 +821,8 @@ int16 GfxMgr::priorityToY(int16 priority) {
return (priority - 5) * 12 + 48;
}
- // dynamic priority bands were introduced in 2.936 (effectively last version of AGI2)
+ // Dynamic priority bands were introduced in 2.425, but removed again until 2.936 (effectively last version of AGI2)
+ // They are available from 2.936 onwards.
// It seems there was a glitch, that caused priority bands to not get calculated properly.
// It was caused by this function starting with Y = 168 instead of 167, which meant it always
// returned with 168 as result.
@@ -832,6 +833,8 @@ int16 GfxMgr::priorityToY(int16 priority) {
// drawn first, followed by ego, which would then draw ego over the dwarf.
// For more information see bug #1712585 (dwarf sprite priority)
//
+ // This glitch is definitely present in 2.425, 2.936 and 3.002.086.
+ //
// Priority bands were working properly in: 3.001.098 (Black Cauldron)
uint16 agiVersion = _vm->getVersion();