I am testing the Qt 4.5.0 Tech Preview on a custom Windows CE device, and
have two problems to relay.  First, as background, this is a Windows
Embedded CE 6.0 R2 device (not Windows Mobile) using an x86 chip and the
Visual Studio 2008 compiler.  I have created an mkspecs file that
corresponds properly to this configuration.  Since this is a custom device,
it is using the corresponding custom SDK.

 

1) During compilation, the WebKit module has several errors related to
functions that would normally be declared in time.h.  The custom SDK for
this CE device does contain time.h, but all Windows CE devices omit
implementations of these functions.  I found that Qt 4.5.0 TP1 has
implementations of these functions in
src\3rdparty\webkit\JavaScriptCore\os-wince\ce_time.cpp.  However, since the
function prototypes are missing from CE's time.h, the compiler still errors
out indicating the functions as missing.  To work around this, I created a
file called ce_time.h alongside ce_time.cpp that simply provides function
prototypes; I then conditionally included this file in the needed WebKit
source files if PLATFORM(WIN_CE) is true.  Doing this allows everything to
compile properly.

 

2) When deployed to the device, most sample applications fail with a dialog
indicating the application "encountered a serious error and must shut down".
I have been able to determine that this is related to text rendering.
Examples that don't use text, such as collidingmice and mandelbrot run just
fine.  Examples that have minimal text such as threadedfortuneserver also
work, but the text is not rendered properly - it is mostly blank with a few
characters drawing glyphs that are seemingly random dot patterns.  The
drilldown example comes up with similarly rendered text below the images,
and clicking on any of the images causes the application to crash once it
brings up the drill down window (which has a lot of text).  It seems that
attempting to render specific characters is causing the crash, but in all
cases, the text is not rendering properly.  Is this perhaps a problem with
raster versus true type fonts?  The custom CE device I have built uses true
type fonts, so raster fonts are not present.

 

I should note that with Qt 4.4.3, everything works properly on the device,
with the exception of font antialiasing and outlines which I reported
earlier (and which appears to be an inherent CE limitation since the Win32
functions to obtain font outlines are not present in CE).

 

-Mark

 

_______________________________________________
Qt4-preview-feedback mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt4-preview-feedback

Reply via email to