Hi,
Phil Thompson of PyQt fame brought the related blogs and finally this ML to
my attention. Thanks, Phil.
This all describes a bright future of our beloved framework INCLUDING a path
onto current mobile platforms. Cool, guys. Thanks.
Hopefully you get the QML-C++ API issue sorted out properly. As long as it
is going to be possible to generate dynamic dialogs with QML widgets
programmatically using official C++ calls, things like dynamically
generated forms and generic SQL query dialogs keep being possible with QML
(something we're doing all the time with PyQt). Or do you really want us
generate QML sourcecode, only to feed the result to the JS interpreter?
Will not try to find words about such an "architecture" now...
Sorry for degression and back to subject.
While I understand, that QWidgets are getting the lower echelons, I feel
like asking about tackling one major show stopper in certain Qt scenarios:
http://bugreports.qt.nokia.com/browse/QTBUG-277
It's about QDateEdit, QTimeEdit and QDateTimeEdit allowing to keep invalid
dates, times and datetimes invalid (with databases, a NULL value of such a
field usually has a special meaning (think "death-day" of still living
people). Current behavior since Qt3 is: if the user just tabs over such a
field, the widgets force a valid date/time value: leading to 2000-01-01
00:00:00 for a QDateTimeEdit. Needless to say, that this behavior isn't
desired almost all the time.
While the bug says, that QDateTime needs modifications, but didn't describe,
which, I beg to differ. What it takes is keeping invalid QDates and QTimes
as long as the user doesn't change one value at least and allowing the user
to invalidate the values.
Could we get this addressed in Qt5, please?
Thanks in advance,
Pete
_______________________________________________
Qt5-feedback mailing list
[email protected]
http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
