Hi John, In a KDateTimeEdit, changing the date in the date combo (whether by typing or selecting e.g. "next month" in the popupmenu), does NOT change the value of date(), which uses its own member variable, unaffected by user interaction.
(tested in the kdelibs KDE/4.14 branch, I suppose frameworks is the same) This unittest shows the same problem, in an automated way: http://www.davidfaure.fr/2015/kdatetimeedittest.diff I suppose the fix would be something around "connecting to the dateEntered signal of the KDateCombo", and similar things with the other widgets. Or possibly not having a member variable, and digging into the date and time combos instead? This makes KDateTimeEdit basically unusable, but fortunately (or maybe for that reason) it's not actually used :-) http://lxr.kde.org/ident?_i=KDateTimeEdit&_remember=1 This gives two options: 1) fixing KDateTimeEdit 2) deprecating KDateTimeEdit (for the usage I'm looking for, a date combo with a calendar popup, QDateEdit should do the job just fine). But I guess it can be useful for other more advanced usages (calendar system choice; date and time; etc.) -- David Faure | david.fa...@kdab.com | Managing Director KDAB France KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.fr KDAB - The Qt Experts _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
