This article lists some known issues in the Qt-4.6.2 for developers to check. Contents
[Hide] * 1 {
Tagshow (Event)
} "> Compile
* 2 Symbian Simulator
* 3 mobile phone {
Tagshow (Event)
} "> Installation
* 4 General Problems (qtcore and qtgui)
* 5 qtnetwork Problems
* 6 questions about qtwebkit
* 7 BUG Tracking Compile * You cannot use gcce to compile the QT library.
* The # include <qttest> format cannot be used to introduce header files in rvct. The # include <qttest/qttest> format must be used.
* Makefile generated by the qmake command must be run by GNU make. make.exe in Symbian sdkscan meet the requirements. If you call make.exe programs that are not compatible with GNU make.exe (for example, make.exe in arm rvct), you may not be able to use makefile correctly.
* The wrapper makefiles created by qmake may cause conflicts with Raptor's make engine, the workaround is to run SBS directly or to use a GNU make with a different EXE name (e.g. the mingw32-make.exe) to run the wrapper makefiles. Symbian Simulator * Multiple applications cannot be started simultaneously in the simulator. When the second application is started, kerrnotsupported (-5) is returned ).
* The emulator (32-bit Windows Application) is limited to 2 GB address space. mwccsym2 links the debug symbols into the executable creating big chunks of memory, this causes a situation where even a small chunk of linear memory is too much to fit into the memory causing application/emulator just bails out without any error note. error is easy to spot if the executable dies before reaching main () and you have just increased epocheapsize maximum in. pro file.
* Changing megabytesoffreememory crashes s60 3rd edition FP 1-emulator at start up. Mobile phone installation * If you already have an old version on your phone, you may fail to install QT. Sis. Delete the technical preview version from your mobile phone and reinstall it.
* If you install the QT library externally {
Tagshow (Event)
} "> On the memory card, because Symbian performs an additional check on the library files on the external memory card, it will be slow to start the QT application. Therefore, the QT library can only be installed in the mobile phone memory (C: disk ).
* QT. Sis binary for mobile phone installation {
Tagshow (Event)
} "> The code instruction set is armv6. Mobile phones such as n96 that do not support armv6 cannot run QT applications. General problems (qtcore and qtgui) * Some Widgets may go beyond the screen, even if you call widget. showfullscreen ().
* Running applications with high CPU load for a long time may cause the program to start manager {
Tagshow (Event)
} "> Process (such as Application List {
Tagshow (Event)
} "> Menu) crash and the viewsrv application is terminated.
* Qlocal and q1_topservices do not work properly in s60 3rd FP1.
* Q {
Tagshow (Event)
} "> Filesystemmodel sometimes creates duplicate nodes for files and directories if the file name and path case doesn't match exactly the case of the file name in the file system.
* Rendering of verticals and very large fonts is not yet in the optimal state.
* "About QT "{
Tagshow (Event)
} "> The dialog box is too large and cannot be {
Tagshow (Event)
} "> Scroll, so the s60 cannot match the normal display of the screen
* The IAP (Internet Access Point) Selection box is displayed every time a socket connects to the network. If you do not want to repeat the selection, you can refer {
Tagshow (Event)
} "> FTP or anomaly in examples, the two programs demonstrate how to use the default connection.
* When the mouse is pressed and dragged, sometimes the mouse event cannot be sent to the correct recipient.
* Using virtual keyboard to edit {
Tagshow (Event)
} "> Qlineedit that has input mask only works pro {
Tagshow (Event)
} "> Perly if masked characters are filled in order starting from the beginning of the string.
* Using qwidget: lower () on a top level window will put the whole application to background. this will most likely be solved in the future by introducing separate window groups for each top level window. note that this solution may impact the contents of the task switcher, making each top level window show up as a separate task.
* For some QT demo applications, in s60 3.x {
Tagshow (Event)
} "> It may take several seconds for the system to switch the display direction of the screen on N95. Qtnetwork Problems * Networkservices is required for network applications. Add target. Capability = networkservices to the. Pro file.
* When you select IAP (Internet Access Point) and wait for the "preshared key for WLAN" dialog box for a long time, the network example program will crash (viewsrv 11 ).
* The network example program uses the first IAP (Internet Access Point), which may cause some connection problems (for example, the MMS access point is working during connection) Qtwebkit Problems * The networkservices capability is required for WebKit applications. Add target. Capability = networkservices to the. Pro file.
* Add the target. epocheapsize 0x200000 0x2000000 statement to. Pro. The minimum heap size of your application is 2 MB and the maximum heap size is 32 MB.
* To run a WebKit application in the simulator, you need to increase the memory space in most cases. Modify the megabytesoffreemory option in the % epocroot %/epoc32/data/EPOC. ini file.
* Using the "-FPU vfpuv2" parameter to compile WebKit will cause random crash (Kern-exec 3) when running JavaScript code ).
* WebCore. Pro can only be compiled in the command line. Compiling in carbide may result in memory depletion errors.
* In armv5, qtwebkit can only be compiled into the release mode. Compiling to debug mode will cause the rvct linked program to run out of memory. Bug Tracking * If you want to learn more about the bug report on the Qt-4.6.x, which has been resolved or not resolved, visit the bug tracker
* This is a public bug tracking system. If you find any new bugs, click the "Create New Issue" link to link the report (which must be a registered user ). Known issues QT 4.6.2symbianAlso see common questions in symbianfaq. Compiling
- Qt libraries cannot be compiled with gcce.
- Header validation sion like # include <qttest> won't work for rvct. Use # include <qttest/qttest> instead.
- The wrapper makefiles created by qmake require GNU make to execute, the make.exe In the Symbian sdks is sufficient for this. if you have an incompatible make.exe in your path (e.g. the one installed by arm rvct), the wrapper makefiles may fail.
- The wrapper makefiles created by qmake may cause conflicts with Raptor's make engine, the workaround is to run SBS directly or to use a GNU make with a different EXE name (e.g. the mingw32-make.exe) to run the wrapper makefiles.
Symbian emulator
- Running multiple QT applications in emulator is not possible. Starting second application will return kerrnotsupported (-5 ).
- The emulator (32-bit Windows Application) is limited to 2 GB address space. mwccsym2 links the debug symbols into the executable creating big chunks of memory, this causes a situation where even a small chunk of linear memory is too much to fit into the memory causing application/emulator just bails out without any error note. error is easy to spot if the executable dies before reaching main () and you have just increased epocheapsize maximum in. pro file.
- Changing megabytesoffreememory crashes s60 3rd edition FP 1-emulator at start up.
Installation on the phone
- Installing the QT. Sis, that is shipped with the package, may fail due to stale state on the phone. Please Uninstall any technology preview version from the phone, and repeat the installation once more.
- If QT libraries are installed to memory card, startup of QT applications is very slow due to Symbian doing additional checking of libraries found from removable media. therefore, QT libraries can only be installed to the phone memory (C :).
- Distributed QT. Sis packages contain binaries built with armv6, making it impossible to run them on n96, which doesn't support armv6.
General issues (qtcore and qtgui)
- Sometimes widgets can grow out of the screen boundaries even with widget. showfullscreen ()
- Apps that cause heavy CPU load for long periods can crash the launching process (e.g. Application menu) with viewsrv 11 panic.
- Qlocale Symbian system locale support and q1_topservices do not work properly in s60 3rd edition FP 1 builds/devices.
- Qfilesystemmodel sometimes creates duplicate nodes for files and directories if the file name and path Case doesn't match exactly the case of the file name in the file system.
- Font rendering: vertical and very big fonts do not yet get rendered optimally.
- The "About QT" dialog is too big and impossible to scroll, therefore not fitting properly fit properly on s60 device screen.
- IAP query dialog can be displayed each time socket tries to connect. For workaround please look at source code for FTP or anomaly examples. There you can see how to set default IAP.
- Mouse events are not always sent to the correct receiver er when pressing down and dragging.
- Using virtual keyboard to edit qlineedit that has input mask only works properly if masked characters are filled in order starting from the beginning of the string.
- Using qwidget: lower () on a top level window will put the whole application to background. this will most likely be solved in the future by introducing separate window groups for each top level window. note that this solution may impact the contents of the task switcher, making each top level window show up as a separate task.
- Switching orientation on a s60 3.x (like the N95) takes several seconds for some QT demos. See Bug report here
Qtnetwork specific issues
- Requires networkservices capability to connect to Internet. Remember to add target. Capability = networkservices in. Pro file.
- Network Using examples might crash (viewsrv 11) when selecting IAP and while waiting for some longer time in "pre-shared key for WLAN" dialog.
- Network Using examples will use first active IAP and that might cause connectivity issues in some cases (I. e. MMS access point in use at that time ).
Qtwebkit specific issues
- Requires networkservices capability to connect to Internet. Remember to add target. Capability = networkservices in. Pro file.
- Add target. epocheapsize 0x200000 0x2000000 in. Pro files. This will set your minimum application heap size to 2 MB and the maximum to 32 MB.
- Running WebKit examples will in most cases require you to increase memory usage of the emulator which can be done by editing megabytesoffreemory setting in % epocroot %/epoc32/data/EPOC. ini.
- Building WebKit with-FPU vfpuv2 causes random crashes (Kern-exec 3) when running JavaScript code.
- WebCore. Pro must be built from command line, building from carbide runs out of memory.
- Qtwebkit can only be build for release mode in armv5. building debug will cause the rvct linker to run out of memory.
Bug tracker
- A list of bugs reported on 4.6.x, which are fixed in 4.6.1 or later (or not fixed yet) can be seen at the bug tracker
- This is a public bug tracker, so you can report any newly discovered bugs using the "Create New Issue" Link (after registering)
|
