Eliminate GCC signed/unsigned warnings related to encodings: The
encoding in the RFB protocol has always been signed, and signed values
are also used in the specification (ie DesktopName = -307 etc). In the
code, however, unsigned types were used in a number of places, but not
all, which causes warnings. This patch fixes the problem by switching
to signed values everywhere.
git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@3968 3789f03b-4d11-0410-bbf8-ca57d06f2519
diff --git a/common/rfb/ConnParams.h b/common/rfb/ConnParams.h
index 7779640..54b5ada 100644
--- a/common/rfb/ConnParams.h
+++ b/common/rfb/ConnParams.h
@@ -66,10 +66,10 @@
const char* name() { return name_; }
void setName(const char* name);
- rdr::U32 currentEncoding() { return currentEncoding_; }
+ rdr::S32 currentEncoding() { return currentEncoding_; }
int nEncodings() { return nEncodings_; }
- const rdr::U32* encodings() { return encodings_; }
- void setEncodings(int nEncodings, const rdr::U32* encodings);
+ const rdr::S32* encodings() { return encodings_; }
+ void setEncodings(int nEncodings, const rdr::S32* encodings);
bool useCopyRect;
bool supportsLocalCursor;
@@ -91,7 +91,7 @@
PixelFormat pf_;
char* name_;
int nEncodings_;
- rdr::U32* encodings_;
+ rdr::S32* encodings_;
int currentEncoding_;
char verStr[13];
int verStrPos;