Custom Query (301 matches)
Results (49 - 51 of 301)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#83 | invalid | QWidget::create() | ||
Description |
while testing blubbels i saw the following: QWidget::create(): WinCreateWindow?(WC_FRAME) failed with 0x00081034 QWidget::create(): WinCreateWindow? failed with 0x00081001 when building the app as debug app all works game.cpp needs a #ifndef Q_OS_OS2 search for use_sound = on; and change this to #ifndef Q_OS_OS2 use_sound = on; #else use_sound = false; #endif |
|||
#84 | fixed | Add DosSetExtLIBPATH to QProcess() | ||
Description |
There is a common problem of searching for the right DLLs for the application being started in OS/2: by default, the OS/2 loader doesn't search for DLLs in the directory where the .exe is located (which is a very common and natural case) which requires to put the DLL to the system DLL location (badly bloating it) or craft a .cmd that sets a proper BEGINLIBPATH/ENDLIBPATH. Both ways suck. I've got an idea to do DosSetExtLIBPATH() with the exe's path implicitly in QProcess before starting the application (and undo afterwards) to make this search location transparent both for the end user and for the Qt developer. Unless I discover some bad side effects, I'll do it like that. |
|||
#85 | wontfix | QProcess: Support P_SESSION | ||
Description |
Currently, the necessary P_SESSION and P_DETACH functionality in QProcess is implemented using workarounds which proxy the calls through "cmd.exe /c" (see #72). This is done so because kLIBC 0.6.3 doesn't support P_SESSION and P_DETACH. Later, we plan to apply a patch to kLIBC that adds support for these execution modes and make use of them in QProcess. This defect is to track this plan. |