Custom Query (301 matches)
Results (37 - 39 of 301)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#149 | wontfix | VLC blocked when opening a non-existent file and quitting | ||
Description |
Hi/2. As subject, VLC is blocked if failing to open a file. The blocked codes are signaling parts. QVLCApp::triggerQuit(); and The QVLCApp class is class QVLCApp : public QApplication { Q_OBJECT public: QVLCApp( int & argc, char ** argv ) : QApplication( argc, argv, true ) { connect( this, SIGNAL(quitSignal()), this, SLOT(quit()) ); } static void triggerQuit() { QVLCApp *app = qobject_cast<QVLCApp*>( instance() ); if ( app ) emit app->quitSignal(); } #if defined (Q_WS_X11) QVLCApp( Display *dp, int & argc, char ** argv ) : QApplication( dp, argc, argv ) { connect( this, SIGNAL(quitSignal()), this, SLOT(quit()) ); } #endif #if defined(Q_WS_WIN) protected: virtual bool winEventFilter( MSG *msg, long *result ) { switch( msg->message ) { case 0x0319: /* WM_APPCOMMAND 0x0319 */ DefWindowProc( msg->hwnd, msg->message, msg->wParam, msg->lParam ); break; } return false; } #endif signals: void quitSignal(); }; |
|||
#258 | wontfix | Use qt4 as the root directory rather than qt4-<version of qt> | ||
Description |
A simple request which makes updating qt4 much easier for those of us who prefer zip files to rpm/yum. By having the "root" directory as simply qt4 rather than qt4-<version number> the steps required to update qt4 are simply 1] delete existing qt4 directory (might be an idea to make a copy 1st in case of problems with the update) 2] unzip new qt4 package to the location of the previous qt4 package The above means no fannying around changing path and libpath in config.sys file to reflect the qt4-<version number> and no reboot necessary. Hope you do not mind the suggestion... |
|||
#215 | invalid | Use mouse button that is configured in OS/2 / eCS for drag and drop (right mouse button by default) | ||
Description |
At the moment I can drag text in TexmakerX and Quassel using the left mouse button (like in windows). This is not in line with standard mouse behavior under OS/2 and eCS. Drag and drop actions should be performed with whatever is configured in the mouse setup object (page buttons and left/or right handed user). |