From 3b23345a0f1d25d20f5b1d7fd051406d45ea1042 Mon Sep 17 00:00:00 2001 From: taeyoon Date: Sat, 18 Jun 2016 13:58:06 +0900 Subject: [PATCH] Revert "[3.0] Change 'char' type to 'signed char'" This reverts commit 942e29e28862a65390be5163c225f67ead10801a. Change-Id: I6f81db36325a832fea60eae1c8f4374eef5ab398 --- .../internal/controls/renderers/svg/nanosvg/nanosvgrast.cc | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/dali-toolkit/internal/controls/renderers/svg/nanosvg/nanosvgrast.cc b/dali-toolkit/internal/controls/renderers/svg/nanosvg/nanosvgrast.cc index a6c843e..a3f3bdb 100644 --- a/dali-toolkit/internal/controls/renderers/svg/nanosvg/nanosvgrast.cc +++ b/dali-toolkit/internal/controls/renderers/svg/nanosvg/nanosvgrast.cc @@ -878,11 +878,12 @@ 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