From 520c05ef06ce203ad32470730f68402bc7719157 Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Mon, 27 Feb 2012 02:13:42 -0600 Subject: Automated update from qt3 --- doc/porting2.doc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/porting2.doc') diff --git a/doc/porting2.doc b/doc/porting2.doc index 26ff61b59..5b70b5fda 100644 --- a/doc/porting2.doc +++ b/doc/porting2.doc @@ -576,10 +576,10 @@ be in the more efficient order (for typical contemporary hardware). If your code made assumptions about the order, you will get blue where you expect red and vice versa (you'll not notice the problem if you use shades of gray, green, or magenta). You should port your code to use the -creator function qRgb(int r,int g,int b) and the -access functions qRed(QRgb), qBlue(QRgb), and qGreen(QRgb). +creator function tqRgb(int r,int g,int b) and the +access functions tqRed(QRgb), tqBlue(QRgb), and tqGreen(QRgb). If you are using the alpha channel, it hasn't moved, but you should use -the functions qRgba(int,int,int,int) and qAlpha(QRgb). Note also that +the functions tqRgba(int,int,int,int) and tqAlpha(QRgb). Note also that QColor::pixel() does not return a QRgb (it never did on all platforms, but your code may have assumed so on your platform) - this may also produce strange color results - use QColor::rgb() if you want a QRgb. -- cgit v1.2.1