[Qt-interest] configure-flags: 3.3 vs 4.5 [embedded]

[Donal]

If you compile the examples, there should be a frame buffer test application
in /examples/qws/framebuffer

That gives you an idea of bit arrangements.

I had a problem with 16bit color where in fact it was 15 bits with one used
for alpha but this bit was placed in a none standard location, right in the
middle of the bit arrangements rather than the MSB or LSB.
While QT 3.3 didn't support these bits, it just worked normally using the
alpha bit as a least significant green bit and that worked as it was
supposed to be used like that.
However, in QT 4.x, it tried to use the alpha bit but in wrong place and
display came out all wrong.

I don't know if you have similar problem but seems to look like it, though
only 4 bits of color.

Regards,
Donal

On Sun, Mar 22, 2009 at 3:12 PM, Karl Krach <mailinglists at bluespirit.la>wrote:

> Hello,
>
> I'm working on an embedded hardware, running a 2.4 kernel with qt 3.3.
> Now I'm evaluating qt 4.5 on the same device. My problem: A simple demo
> app with a single combo box looks on the qt 3.3 quite nice, compiled
> with qt 4.5 it looks really ugly.
>
> Two screenshots to compare:
> http://www.bluespirit.la/tmp/arm_qt33_combo.jpg
> http://www.bluespirit.la/tmp/arm_qt45_combo.jpg
>
> Both is 'out of the box'. Both is compiled with '-depth 4', because I
> have only a 4bit grayscale display.
>
> Theses are my qt 4.5 configure flags:
> ../qt-embedded-linux-commercial-src-4.5.0/configure -prefix
> /home/KKrach/programs/arm-qt-embedded-4.5.0 -prefix-install -embedded
> arm -xplatform qws/linux-arm-g++ -depths 4 -optimized-qmake -no-armfpa
> -no-opengl -no-glib -no-exceptions -no-accessibility -no-qt3support
> -no-phonon -no-phonon-backend -no-svg -no-webkit -no-scripttools
> -no-openssl -no-stl -no-nis -nomake "examples demos docs" -no-gif
> -no-libtiff -qt-libpng -no-libmng -no-sql-sqlite -no-mouse-pc
> -no-mouse-bus -no-mouse-yopy -no-mouse-linuxtp -qt-kbd-usb -qt-gfx-vnc
> -qt-gfx-linuxfb -qt-gfx-qvfb -qt-gfx-transformed -no-gfx-multiscreen
> -confirm-license
>
> and these the qt 3.3 configure flags:
> /opt/qt/arm/qt-embedded-commercial-3.3.2-xml/configure -embedded arm
> -debug -thread -shared -disable-canvas -disable-sql -disable-opengl
> -enable-xml -qt-imgfmt-jpeg -qt-imgfmt-png -no-imgfmt-mng -no-stl
> -depths 4 -qvfb -qt-gfx-vnc -qt-gfx-raster -qt-gfx-qvfb
> -qt-gfx-transformed -qt-kbd-usb -no-mouse-pc -no-mouse-bus
> -no-mouse-yopy -no-mouse-linuxtp -no-gfx-mach64 -no-gfx-matrox
> -no-gfx-vga16-no-gfx-voodoo -no-gfx-snap -no-imgfmt-mng -no-imgfmt-jpeg
> -no-cups -no-nis -no-style-platinum -disable-workspace -no-gfx-snap
>
> If I printf the depth information of QScreen, I get the following output:
> ./arm-qt-test -qws
> QScreen supports 4Bit: true
>  physicalHeight= 113
>  physicalWidth = 169
>  pixelFormat   = 0
>  depth         = 4
>  pixmapDepth   = 4
>
>
> Do you have any suggestions, what I can try to get a better
> visualization on the screen?
>
> Thanks,
> Charly
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at trolltech.com
> http://lists.trolltech.com/mailman/listinfo/qt-interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20090322/bb7bc90b/attachment.html