diff options
| author | Johannes Schickel | 2013-08-06 22:31:36 +0200 |
|---|---|---|
| committer | Narek Mailian | 2013-08-22 11:46:49 +0200 |
| commit | af13b74d023c3f7880f1b06f427d3b69e5c8831e (patch) | |
| tree | a753f3a54a91d69f1ce1eb3bfb562e3bf3775b00 /devtools | |
| parent | 81ae06cae36a398c4126cfa80022677703e9ab57 (diff) | |
| download | scummvm-rg350-af13b74d023c3f7880f1b06f427d3b69e5c8831e.tar.gz scummvm-rg350-af13b74d023c3f7880f1b06f427d3b69e5c8831e.tar.bz2 scummvm-rg350-af13b74d023c3f7880f1b06f427d3b69e5c8831e.zip | |
GRAPHICS: Unify drawing paths in VectorRendererSpec::drawString.
Formerly, the behavior between when a drawable area was specified and when not
was different in a sense which is not expected. For example, when an empty
textDrawableArea was passed and the text could be drawn outside the 'area'
specified. While when a textDrawableArea covering the whole screen was passed
the text was clipped inside 'area'. Now, the code does follow the latter logic
in both cases.
I am not sure whether this will cause any issues, but a quick check of the
launcher and options menu didn't reveal anything...
Diffstat (limited to 'devtools')
0 files changed, 0 insertions, 0 deletions