Added kmymoney

git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/applications/kmymoney@1239792 283d02a7-25f6-0310-bc7c-ecb5cbfe19da

1 files changed, 438 insertions, 0 deletions

diff --git a/libkdchart/KDChartWidget.cpp b/libkdchart/KDChartWidget.cpp
new file mode 100644
index 0000000..81164ea
--- /dev/null
+++ b/libkdchart/KDChartWidget.cpp
@@ -0,0 +1,438 @@
+/* -*- Mode: C++ -*-
+   KDChart - a multi-platform charting engine
+   */
+
+/****************************************************************************
+ ** Copyright (C) 2001-2003 Klarälvdalens Datakonsult AB.  All rights reserved.
+ **
+ ** This file is part of the KDChart library.
+ **
+ ** This file may be distributed and/or modified under the terms of the
+ ** GNU General Public License version 2 as published by the Free Software
+ ** Foundation and appearing in the file LICENSE.GPL included in the
+ ** packaging of this file.
+ **
+ ** Licensees holding valid commercial KDChart licenses may use this file in
+ ** accordance with the KDChart Commercial License Agreement provided with
+ ** the Software.
+ **
+ ** This file is provided AS IS with NO WARRANTY OF ANY KIND, INCLUDING THE
+ ** WARRANTY OF DESIGN, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
+ **
+ ** See http://www.klaralvdalens-datakonsult.se/?page=products for
+ **   information about KDChart Commercial License Agreements.
+ **
+ ** Contact [email protected] if any conditions of this
+ ** licensing are not clear to you.
+ **
+ **********************************************************************/
+#include <KDChartWidget.h>
+#include <KDChart.h>
+#include <KDChartParams.h>
+#include <KDChartTableBase.h>
+#ifndef KDCHART_MASTER_CVS
+#include "KDChartWidget.moc"
+#endif
+
+#include <qpainter.h>
+
+/**
+  \class KDChartWidget KDChartWidget.h
+
+  \brief The entry point into the charting that most people will want
+  to use.
+
+  Simply create a KChartWidget in your application and put it where
+  you want in your widget hierarchy and create a KChartParams object
+  that specifies how the chart should be drawn.
+
+  \note If for some reason you are NOT using the
+  KDChartWidget class but calling the painting methods of KDChart directly,
+  you probably will also use the KDChartDataRegionList class:
+  This class is derived from QPtrList, so all of the Qt documentation
+  for this class is valid for KDChartDataRegionList too, e.g. freeing
+  of the pointers stored can either be done automatically or
+  manually - so PLEASE take the time to read the reference information for this class!
+
+  \sa KDChart, KDChartDataRegionList
+  */
+
+
+/**
+  Default Constructor.
+
+  Sets params and data pointers to zero, you should call setParams
+  and setData before using this chart otherwise only a simple
+  default bar chart will be shown.
+
+  \param parent the widget parent; passed on to QWidget
+  \param name the widget name; passed on to QWidget
+  */
+
+KDChartWidget::KDChartWidget( QWidget* parent, const char* name ) :
+QWidget( parent, name ),
+    _params( 0 ),
+    _data( 0 ),
+    _activeData( false ),
+_mousePressedOnRegion( 0 )
+{
+    _dataRegions.setAutoDelete( true );
+    setDoubleBuffered( true );
+    setBackgroundMode( Qt::NoBackground );
+}
+
+
+/**
+  Constructor. Stores the chart parameters.
+
+  \param params the specification of the chart
+  \param data the data to be displayed as a chart
+  \param parent the widget parent; passed on to QWidget
+  \param name the widget name; passed on to QWidget
+  */
+
+KDChartWidget::KDChartWidget( KDChartParams* params,
+        KDChartTableDataBase* data,
+        QWidget* parent, const char* name ) :
+QWidget( parent, name ),
+    _params( params ),
+    _data( data ),
+    _activeData( false ),
+_mousePressedOnRegion( 0 )
+{
+    _dataRegions.setAutoDelete( true );
+    setDoubleBuffered( true );
+    setBackgroundMode( Qt::NoBackground );
+}
+
+
+/**
+  Destructor.
+  */
+KDChartWidget::~KDChartWidget()
+{
+    // delete any regions that might still be registered
+    _dataRegions.clear();
+    KDChartAutoColor::freeInstance();
+}
+
+void KDChartWidget::paintTo( QPainter& painter,
+        const QRect* rect )
+{
+    KDChart::paint( &painter, _params, _data, &_dataRegions, rect );
+}
+
+void KDChartWidget::print( QPainter& painter,
+        const QRect* rect )
+{
+    bool oldOpt=true;
+    if( _params ){
+        oldOpt = _params->optimizeOutputForScreen();
+        _params->setOptimizeOutputForScreen( false );
+    }
+    bool bOldBuf = _doubleBuffered;
+    _doubleBuffered = false;
+    paintTo( painter, rect );
+    _doubleBuffered = bOldBuf;
+    if( _params )
+        _params->setOptimizeOutputForScreen( oldOpt );
+}
+
+void KDChartWidget::paintEvent( QPaintEvent* event )
+{
+    if( _doubleBuffered ) {
+        // if double-buffering, paint onto the pixmap and copy
+        // afterwards
+        _buffer.fill( backgroundColor() );
+        QPainter painter( &_buffer );
+        paintTo( painter );
+        bitBlt( this, event->rect().topLeft(), &_buffer, event->rect() );
+    } else {
+        // if not double-buffering, paint directly into the window
+        QPainter painter( this );
+        paintTo( painter );
+    }
+}
+
+
+/**
+  \internal
+  */
+void KDChartWidget::mousePressEvent( QMouseEvent* event )
+{
+    if ( !_activeData )
+        return ;
+
+    _mousePressedOnRegion = 0;
+    KDChartDataRegion* current = 0;
+    //QPtrListIterator < KDChartDataRegion > it( _dataRegions );
+    for( current = _dataRegions.last(); current; current = _dataRegions.prev() ){
+    //while ( ( current = it.current() ) ) {
+        if ( current->contains( event->pos() ) ) {
+            _mousePressedOnRegion = current;
+            if ( event->button() == LeftButton ){
+                emit dataLeftPressed( current->row, current->col );
+                emit dataLeftPressed( event->pos() );
+            }else if ( event->button() == MidButton ){
+                emit dataMiddlePressed( current->row, current->col );
+                emit dataMiddlePressed( event->pos() );
+            }else{
+                emit dataRightPressed( current->row, current->col );
+                emit dataRightPressed( event->pos() );
+            }
+            return;
+        }
+    }
+}
+
+
+/**
+  \internal
+  */
+void KDChartWidget::mouseReleaseEvent( QMouseEvent* event )
+{
+    if ( !_activeData )
+        return ;
+
+    KDChartDataRegion* current = 0;
+    QPtrListIterator < KDChartDataRegion > it( _dataRegions );
+    while ( ( current = it.current() ) ) {
+        ++it;
+        if ( current->contains( event->pos() ) ) {
+            if ( event->button() == LeftButton ) {
+                emit dataLeftReleased( current->row, current->col );
+                emit dataLeftReleased( event->pos() );
+                if ( _mousePressedOnRegion == current ){
+                    emit dataLeftClicked( current->row, current->col );
+                    emit dataLeftClicked( event->pos() );
+                }
+            } else if ( event->button() == MidButton ) {
+                emit dataMiddleReleased( current->row, current->col );
+                emit dataMiddleReleased( event->pos() );
+                if ( _mousePressedOnRegion == current ){
+                    emit dataMiddleClicked( current->row, current->col );
+                    emit dataMiddleClicked( event->pos() );
+                }
+            } else {
+                emit dataRightReleased( current->row, current->col );
+                emit dataRightReleased( event->pos() );
+                if ( _mousePressedOnRegion == current ){
+                    emit dataRightClicked( current->row, current->col );
+                    emit dataRightClicked( event->pos() );
+                }
+            }
+        }
+    }
+}
+
+
+/**
+  \internal
+  */
+void KDChartWidget::resizeEvent( QResizeEvent* /*event*/ )
+{
+    // if we use double-buffering, resize the buffer to the new size,
+    // otherwise leave it alone
+    if( _doubleBuffered )
+        _buffer.resize( size() );
+}
+
+
+/**
+  If \a active is true, this widget reports mouse presses, releases
+  and clicks on the data segments it displays. This can slow down the
+  display process, so this is turned off by default.
+
+  If active data reporting is turned on when the widget is already
+  shown, data will be reported after the next repaint(). Call
+  repaint() explicitly if necessary.
+
+  Active data is currently supported for bar, pie, and line charts
+  (the latter only with markers, as trying to hit the line would be
+  too difficult for the user anyway).
+
+  \param active if true, the widget reports mouse events
+  \sa isActiveData()
+  */
+void KDChartWidget::setActiveData( bool active )
+{
+    _activeData = active;
+}
+
+
+/**
+  Returns true if the widget is configured to report mouse
+  events. The default is not to report mouse events.
+
+  \return true if the widget is configured to report mouse events,
+  false otherwise
+  \sa setActiveData()
+  */
+bool KDChartWidget::isActiveData() const
+{
+    return _activeData;
+}
+
+
+/**
+  If \a doublebuffered is true, the widget will double-buffer
+  everything while drawing which reduces flicker a lot, but requires
+  more memory as an off-screen buffer of the same size as the widget
+  needs to be kept around. However, in most cases, it is worth
+  spending the extra memory. Double-buffering is on by
+  default. Turning double-buffering on or off does not trigger a
+  repaint.
+
+  \param doublebuffered if true, turns double-buffering on, if false,
+  turns double-buffering off
+  \sa isDoubleBuffered
+  */
+void KDChartWidget::setDoubleBuffered( bool doublebuffered )
+{
+    _doubleBuffered = doublebuffered;
+    if( doublebuffered ) {
+        // turn double-buffering on
+        // resize the buffer to the size of the widget
+        _buffer.resize( size() );
+    } else {
+        // turn double-buffering off
+        // minimize the buffer so that it does not take any memory
+        _buffer.resize( 0, 0 );
+    }
+}
+
+
+/**
+  Returns whether the widget uses double-buffering for drawing. See
+  \a setDoubleBuffered() for an explanation of double-buffering.
+
+  \return true if double-buffering is turned on, false otherwise
+  */
+bool KDChartWidget::isDoubleBuffered() const
+{
+    return _doubleBuffered;
+}
+
+
+/**
+  Set an entire new parameter set.
+  (Normally you might prefer modifying the existing parameters
+  rather than specifying a new set.)
+  */
+void KDChartWidget::setParams( KDChartParams* params )
+{
+    _params = params;
+}
+
+/**
+  Set an entire new data table.
+  */
+void KDChartWidget::setData( KDChartTableDataBase* data )
+{
+    _data = data;
+}
+
+/**
+  Returns a pointer to the current parameter set.
+  */
+KDChartParams* KDChartWidget::params() const
+{
+    return _params;
+}
+
+/**
+  Returns a pointer to the current data table.
+  */
+KDChartTableDataBase* KDChartWidget::data() const
+{
+    return _data;
+}
+
+/**
+  \fn void KDChartWidget::barsDisplayed( int barsDisplayed, int barsLeft )
+
+  This signal is emitted when drawing of a bar chart is done.
+  Use it to determine if all bars have been drawn: in case
+  you specified both the bar width and the value block gap width
+  it might be that KD Chart is not able to display all bars since
+  they do not fit into the available horizontal space.
+
+  The value of barsLeft indicates how many bars could not be
+  drawn because the data area was not wide enough.
+
+  \sa KDChartParams::numBarsDisplayed, KDChartParams::numBarsLeft
+  */
+
+/**
+  \fn void KDChartWidget::dataLeftClicked( uint row, uint col )
+
+  This signal is emitted when a data item was clicked onto with the left mouse button.
+
+  The values of row / col indicate the respective dataset (row) and item (col).
+
+  \note There is another signal sent simultaneously: reporting the screen coordinates clicked onto.
+
+  \sa dataLeftReleased
+  \sa dataRightClicked, dataMiddleClicked
+  */
+/**
+  \fn void KDChartWidget::dataRightClicked( uint row, uint col )
+
+  This signal is emitted when a data item was clicked onto with the right mouse button.
+
+  The values of row / col indicate the respective dataset (row) and item (col).
+
+  \note There is another signal sent simultaneously: reporting the screen coordinates clicked onto.
+
+  \sa dataRightReleased
+  \sa dataLeftClicked, dataMiddleClicked
+  */
+/**
+  \fn void KDChartWidget::dataMiddleClicked( uint row, uint col )
+
+  This signal is emitted when a data item was clicked onto with the middle mouse button.
+
+  The values of row / col indicate the respective dataset (row) and item (col).
+
+  \note There is another signal sent simultaneously: reporting the screen coordinates clicked onto.
+
+  \sa dataMiddleReleased
+  \sa dataLeftClicked, dataRightClicked
+  */
+
+/**
+  \fn void KDChartWidget::dataLeftClicked( const QPoint & pnt )
+
+  This signal is emitted when a data item was clicked onto with the left mouse button.
+
+  The value of pnt indicates the screen coordinates in relation to the origin of the data area.
+
+  \note There is another signal sent simultaneously: reporting which data item was clicked onto.
+
+  \sa dataLeftReleased
+  \sa dataRightClicked, dataMiddleClicked
+  */
+/**
+  \fn void KDChartWidget::dataRightClicked( const QPoint & pnt )
+
+  This signal is emitted when a data item was clicked onto with the right mouse button.
+
+  The values of row / col indicate the screen coordinates in relation to the origin of the data area.
+
+  \note There is another signal sent simultaneously: reporting which data item was clicked onto.
+
+  \sa dataRightReleased
+  \sa dataLeftClicked, dataMiddleClicked
+  */
+/**
+  \fn void KDChartWidget::dataMiddleClicked( const QPoint & pnt )
+
+  This signal is emitted when a data item was clicked onto with the middle mouse button.
+
+  The values of row / col indicate the screen coordinates in relation to the origin of the data area.
+
+  \note There is another signal sent simultaneously: reporting which data item was clicked onto.
+
+  \sa dataMiddleReleased
+  \sa dataLeftClicked, dataRightClicked
+  */