documentation improved

doc/classes/QskQuickItem.dox

@@ -3,7 +3,7 @@
 
     \ingroup Framework
 
-    QskQuickItem completes the C++ API of QQuickItem and reestablishs basic
+    QskQuickItem completes the C++ API of QQuickItem and re-establishs basic
     concepts like events. It also offers better control over the operations
     happening in the update cycle.
  */
@@ -599,22 +599,50 @@
 
     QskQuickItem handles the additional type of events.
 
+    For some reason the QQuick classes introduced proprietory notfier hooks
+    instead of using the well established and powerful concept of events.
+    QskQuickItem tries to revert this decision by mapping notifications
+    to events, when possible.
+
+    The following notification events are added by QSkinny - usually with a
+    very similar to how they are used known for Qt/Widgets:
+
+    - QEvent::ContentsRectChange
+    - QEvent::LocaleChange
+    - QEvent::ParentChange
+    - QEvent::EnabledChange
+    - QEvent::ReadOnlyChange
+    - QEvent::LayoutDirectionChange
+    - QEvent::LayoutRequest
+
+    Furthermore events derived from QskEvent are used.
+
     \param event Qt event
 */
 
 /*!
     \fn QskQuickItem::changeEvent
 
-	This event handler can be reimplemented to handle state changes.
-
-	Change events include:
+    This event handler can be reimplemented to handle certain state changes:
 
         - QEvent::StyleChange
         - QEvent::ContentsRectChange
-		- QEvent::EnabledChange
+        - QEvent::FontChange
+        - QEvent::PaletteChange
         - QEvent::ReadOnlyChange
+        - QEvent::EnabledChange
         - QEvent::LocaleChange
         - QEvent::ParentChange
+        - QEvent::LayoutDirectionChange
+
+    
+
+    \param event Qt event
+
+    \note QEvent::PaletteChange, QEvent::FontChange are handled, but both event types
+          do not fit to the themeing concept of QSkinny and are not posted. However
+          it is possible to post them if an application has a concept, where they
+          make sense.
 */
 
 /*!