Commit b70cb5b9 authored by Jean-Baptiste Kempf's avatar Jean-Baptiste Kempf

Qt: s/Qt4/Qt

parent 9720a180
Small Hacking file for the Qt Interface
If you ever code for Qt4 interface, please read this before.
If you ever code for Qt interface, please read this before.
** Code Convetions **
......@@ -18,7 +18,7 @@ Refer to http://wiki.videolan.org/Code_Conventions it should be up to date
- VLC include/*.h includes
- Other VLC .h includes (gruiking :D)
- Qt4 module includes
- Qt module includes
- Qt includes
** Naming **
......@@ -43,7 +43,7 @@ So if your dialog is a dialog you are used to keep during a playing of a video,
QVLCFrame: extended panel, messages...
QVLCDialog: preferences, open...
** HIG for Qt4 **
** HIG for Qt **
We tend to use GNOME/KDE specs over Vista ones for capitalizations:
We use Header for:
- Menu
......
......@@ -56,7 +56,7 @@ public:
playlist_item_t *, QObject *parent = 0 );
virtual ~PLModel();
/* Qt4 main PLModel */
/* Qt main PLModel */
static PLModel* getPLModel( intf_thread_t *p_intf )
{
if(!p_intf->p_sys->pl_model )
......
......@@ -640,8 +640,8 @@ void MainInterface::toggleFSC()
/**
* NOTE:
* You must not change the state of this object or other Qt4 UI objects,
* from the video output thread - only from the Qt4 UI main loop thread.
* You must not change the state of this object or other Qt UI objects,
* from the video output thread - only from the Qt UI main loop thread.
* All window provider queries must be handled through signals or events.
* That's why we have all those emit statements...
*/
......@@ -691,7 +691,7 @@ void MainInterface::releaseVideoSlot( void )
{
/* This function is called when the embedded video window is destroyed,
* or in the rare case that the embedded window is still here but the
* Qt4 interface exits. */
* Qt interface exits. */
assert( videoWidget );
videoWidget->release();
setVideoOnTop( false );
......
......@@ -704,9 +704,9 @@ static void WindowClose( vout_window_t *p_wnd )
QMutexLocker locker (&lock);
/* Normally, the interface terminates after the video. In the contrary, the
* Qt4 main loop is gone, so we cannot send any event to the user interface
* widgets. Ideally, we would keep the Qt4 main loop running until after
* the video window is released. But it is far simpler to just have the Qt4
* Qt main loop is gone, so we cannot send any event to the user interface
* widgets. Ideally, we would keep the Qt main loop running until after
* the video window is released. But it is far simpler to just have the Qt
* thread destroy the window early, and to turn this function into a stub.
*
* That assumes the video output will behave sanely if it window is
......
File mode changed from 100755 to 100644
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment