On Wed, Jul 29, 2015 at 11:47 AM, Marc Mutz wrote:
> On Wednesday 29 July 2015 09:04:42 Martin Klapetek wrote:
> > Can you perhaps create a single diff against 5.5/dev/master
> > which could be easily applied? That should make things
> > much easier to help :)
>
> As
Can you perhaps create a single diff against 5.5/dev/master
which could be easily applied? That should make things
much easier to help :)
Cheers
--
Martin Klapetek | KDE Developer
___
Development mailing list
Development@qt-project.org
http://lists.qt
t your ideas
today and give some feedback as well.
Cheers
--
Martin Klapetek | KDE Developer
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
rid stuff and re-implement the "containsEvents" property to be
> filled with data from akonadi.
How would that be filled with data if it returns boolean? I mean, what do
you want to fill where? :)
Overall I like the real model backend, however I think your proposal also
could
still use the base QAbstractCalendarModel implementation for
> >> it's grid stuff and re-implement the "containsEvents" property to be
> >> filled with data from akonadi.
> >
> >
> > How would that be filled with data if it returns boolean? I mean
y .. 7 = Sunday. There might be more differences.
So you cannot pass direct values between QML and C++ (like passing
QDate::month() to JS), passing whole date objects should be fine afaik (eg.
passing JS Date to a C++ function expecting QDate).
Cheers
--
