Age | Commit message (Collapse) | Author |
|
This is consistent with what happens when checking for "pending U
keys", so I think it's correct, but the Scalpel keyboard handling
doesn't work very well at the moment anyway. Probably at least partly
because of the way it mixes char and Common::KeyCode. I haven't
been able to wrap my head around it...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The changes remove most of the hardcoding that was in place for showing
the conversation movies, and have them triggered like the Rose Tattoo
speech files. It will still need some work to hook it into our new
voice playback, though, so text dialogs are closed at the right time
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Restoring movement across save didn't work, so properly handle
stopping any moving characters when loading a savegame
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
How such string constants are compiled into code depends on the encoding
used for the source file, which easily is changed by accident (e.g.
between UTF-8 and Latin-1 encoding). Better to explicitly encode the
character codes, as is already done for various other text messages.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|