so....

I looked for a problem. could not found due the kind of code structure.
so I had reorganized the code into a more sensefull structure so every one
should be able to find some code sequences when searching for a bug.
yes - now I found the problem and can thinking about resolving it.

1 files changed, 34 insertions, 0 deletions

diff --git a/core/pim/datebook/modules/weeklst/datebookweeklstheader.h b/core/pim/datebook/modules/weeklst/datebookweeklstheader.h
new file mode 100644
index 0000000..818b825
--- a/dev/null
+++ b/core/pim/datebook/modules/weeklst/datebookweeklstheader.h
@@ -0,0 +1,34 @@
+#ifndef _DATEBOOKWEEKLSTHEADER_H

+#define _DATEBOOKWEEKLSTHEADER_H

+

+#include "datebookweeklstheaderbase.h"

+

+#include <qdatetime.h>

+

+class DateBookWeekLstHeader: public DateBookWeekLstHeaderBase

+{

+    Q_OBJECT

+public:

+    DateBookWeekLstHeader(bool onM, QWidget* parent = 0, const char* name = 0,

+              WFlags fl = 0 );

+    ~DateBookWeekLstHeader();

+    void setDate(const QDate &d);

+

+public slots:

+    void nextWeek();

+    void prevWeek();

+    void nextMonth();

+    void prevMonth();

+    void pickDate();

+    void setDate(int y, int m, int d);

+signals:

+    void dateChanged(QDate &newdate);

+    void setDbl(bool on);

+protected:

+    QDate date;

+//  bool onMonday;

+    bool bStartOnMonday;

+

+};

+

+#endif