| Age | Commit message (Collapse) | Author |
|---|
|
|
|
GCC did not warn about these, but surely it should be bitwise OR,
not logical OR, here as well. But I don't think I have any game that
uses MaxTrax (Amiga version of Legend of Kyrandia?), so I can't
really test this.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes #10118.
|
|
|
|
Currently translated at 100.0% (965 of 965 strings)
|
|
It was due to inaccurate rotation movie bounds.
Fixes #10086.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Fixes #10065.
|
|
Fixes #10064
|
|
Fixes #10103.
|
|
Fixes #10108.
|
|
When using keyboard navigation
|
|
One call to va_end was missing when returning early. This stuff is too
dangerous for me to use.
|
|
|
|
|
|
leads to confusion.
|
|
|
|
The movement code, when deciding on an item or link that matches the
desired direction, will check five points on the object/links area..
center, left edge, right edge, top edge, and bottom edge. For each
of these, it makes sure that at that point, clicking will actually
get passed to it. Otherwise, it moves onto one of the other edges.
This helps avoid issues where links weren't working because standard
scene objects were partially obscuring them.
|
