{5} Assigned, Active Tickets by Owner (Full Description) (8 matches)

List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.

dmik (8 matches)

Ticket Summary Component Milestone Type Severity Created
Description
#24 Dummy ticket to experiment with the Admin page [ports] qt-os2-3.3.1-rc06 defect blocker 07/01/06

I want to test how ticket comments can be managed using the corresponding plugin on the Admin page. Added here.

#3 How to report success usage of QT3 for building applications? [ports] task normal 12/07/05

I just made DCGUI QT-based build. Binaries can be downloaded from Netlabs ftp ftp://ftp.netlabs.org/incoming/valknut-3.0.7-os2.zip

#19 Reduce the number of exports in the Qt DLL [general] qt-os2-3.3.1-rc07 task normal 04/06/06

Currently, the Qt DLL exports about 16500 symbols. This amount is quite large and will most likely keep increasing slightly with every new Qt release or a new missing feature added. It's not a problem by itself, but sticks us to a concrete version of the linker: IBM ILINK from the distributioin of IBM Visual Age C/C++ 3.08. The general problem with this linker is that it's not free so that you cannot use it unless you have a valid license of Visual Age C/C++, which is obviously not good for such an open source project the Qt library is. Possibly alternatives include:

  1. ILINK386 from the IBM OS/2 Developer's Toolkit. I haven't used it for Qt but heard that it has various problems related to linking the GCC code containing C++ classes.
  2. ILINK 5.0, freely distributed by IBM (?). Looks like the latest linker for OS/2 made by IBM, but has very strange limitation (seems like a bug actually): the total number of exports cannot exceed 15000 or so. If there are more exports, the DLL just screws up the application using it when the latter gets loaded by the kernel for execution.
  3. WCL386 from the Open Watcom compiler package. Currently, this linker is also not able to link the GCC's C++ code properly. Knut St Osmundsen (the current maintainer and the developer of the OS/2 version of GCC) is currently working on this issue, but we don't know anything yet about its limitation on the number of exports.

The last two can be freely used by anyone, so it would be great if they could be used to link the Qt DLL and Qt applications. Taking the limitations of ILINK 5.0 (and possible limitations of WCL386) into account, it's worth a try to reduce the number of exports in the Qt library.

#22 Implement the Drag & Drop support kernel qt-os2-3.3.1-rc07 enhancement normal 05/02/06

I've decided to implement the Drag & Drop support before the Release Candidate 07 comes out. This is because many existing Qt apps use d&d (at least partly) which makes it difficult to port them with QT_NO_DRAGANDDROP defined.

#28 DBCS don't work properly kernel defect normal 09/02/06

DBCS characters can neither be entered nor displayed correctly. For example, if you set codepage 932 as the system default code page (provided that you have Japanese fonts and other resources installed), open the Qt font dialog, select Times New Roman MT 30 and select, say, the Katakana or Han script (which produces 41 61 42 62 83 4F 83 5F 83 6F 83 80 and 41 61 42 62 90 9F E4 70 8C 65 E8 D9 byte sequences in the Sample field, respectively), you will get Japanese characters overlaid each other. Also, there are reports that it's impossible to enter characters using IME (Input Method Editor).

#30 QProcess's readStdout()/readStderr() is slow kernel qt-os2-3.3.1-rc07 defect normal 09/11/06

QT-based photoproc http://sourceforge.net/project/showfiles.php?group_id=98019 application uses QProcess class to launch 3-rd party text-mode tool. Everything looks-like ok and tool started but nothing happend, like data from tool's stdout doesn't pass to main application.

#34 Spontaneous traps of Qt applications during window management kernel qt-os2-3.3.1-rc07 defect normal 11/12/06

Sometimes, a Qt application just traps in the middle of some window management (assumption). On my system, it happened a couple of times with Psi/2 upon attempts to show tooltips.

#37 Static configurations link aginst wrong .lib kernel defect normal 03/28/08

When Qt is configured as static library, the file that gets created is named "myqt.lib". However, makefiles generated from *.pro will search for "qt.lib".

Changing lines 143 and 144 in mkspecs\os2-g++\qmake.conf

from:

QMAKE_LIBS_QT = qt registry.dll socket QMAKE_LIBS_QT_THREAD = qt registry.dll socket

to:

QMAKE_LIBS_QT = $$QMAKE_QT_DLL_TARGET registry.dll socket QMAKE_LIBS_QT_THREAD = $$QMAKE_QT_DLL_TARGET registry.dll socket

appears to fix this.

Note: See TracReports for help on using and creating reports.