Custom Query (301 matches)
Results (25 - 27 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(); }; |
|||
#150 | wontfix | MOC output on "No relevant classes found" | ||
Description |
This is a rather weird one, but I'm asking for your opinion on that... When MOC processes a file without any "mocable" classes, it creates a zero-length output file. Unfortunately, if the target drive is on a NetWare? server, the timestamp of such a zero-length file is not updated (which is not MOC's fault). Anyway, as a result of that MAKE will re-invoke MOC for those classes - even though nothing has changed - and then cause the empty MOC result to be compiled. Due to this the target will be re-linked, which can be quiet time consuming. A simple workaround for that problem is to always write something into the MOC result files. A carriage return would be sufficient, however I'm wondering why they don't put the standard "this is a MOC generated file blah blah" comment header in... |
|||
#153 | wontfix | Remove the need of GCC422.DLL | ||
Description |
The option "-static-libgcc" applied to the link step seems to do the trick and prevents the users from having to hunt for another DLL. |