From ed648574f04ce428c45474b3ed86076e2e222ebf Mon Sep 17 00:00:00 2001 From: taeyoon Date: Sat, 18 Jun 2016 14:06:45 +0900 Subject: [PATCH] [3.0] Change 'char' type to 'signed char' Change-Id: I020da6f27a90b10048ce02d4922dbdd9b4763727 --- .../internal/controls/renderers/svg/nanosvg/nanosvgrast.cc | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/dali-toolkit/internal/controls/renderers/svg/nanosvg/nanosvgrast.cc b/dali-toolkit/internal/controls/renderers/svg/nanosvg/nanosvgrast.cc index a3f3bdb..a6c843e 100644 --- a/dali-toolkit/internal/controls/renderers/svg/nanosvg/nanosvgrast.cc +++ b/dali-toolkit/internal/controls/renderers/svg/nanosvg/nanosvgrast.cc @@ -878,12 +878,11 @@ static void nsvg__fillScanline(unsigned char* scanline, int len, int x0, int x1, // note: this routine clips fills that extend off the edges... ideally this // wouldn't happen, but it could happen if the truetype glyph bounding boxes // are wrong, or if the user supplies a too-small bitmap - - /** - * In the original file, using char type (without signed or unsigned) can be interpreted - * as 'unsigned char' in some build environments, like ARM architecture. - * To prevent the unexpected behavior, we replace 'char fillRule' with 'signed char fillRule' here. - */ +/** + * In the original file, using char type (without signed or unsigned) can be interpreted + * as 'unsigned char' in some build environments, like ARM architecture. + * To prevent the unexpected behavior, we replace 'char fillRule' with 'signed char fillRule' here. + */ static void nsvg__fillActiveEdges(unsigned char* scanline, int len, NSVGactiveEdge* e, int maxWeight, int* xmin, int* xmax, signed char fillRule) { // non-zero winding fill -- 2.7.4