Re: [Interest] QDateTime uses different time zone offset prior to UNIX epoch?

2019-09-20 Thread Thiago Macieira
On Friday, 20 September 2019 14:20:40 PDT Patrick Stinson wrote: > QDateTime initializes with a different time zone offset when passed a QDate > before versus after Jan 1 1970. The following line says it all: > > QDateTime(QDate(1969, 10, 14)).offsetFromUtc() != QDateTime(QDate(1970, 10, >

[Interest] QDateTime uses different time zone offset prior to UNIX epoch?

2019-09-20 Thread Patrick Stinson
QDateTime initializes with a different time zone offset when passed a QDate before versus after Jan 1 1970. The following line says it all: QDateTime(QDate(1969, 10, 14)).offsetFromUtc() != QDateTime(QDate(1970, 10, 14)).offsetFromUtc() It seems to me that the offsets for these two QDateTime

[Interest] ASSERT failure in QCocoaScreen: "The application's primary screen should always be in sync with the main display"

2019-09-20 Thread Patrick Stinson
I received this error after upgrading from 5.13.0 to 5.13.1 and disconnecting my external monitor from my latest-model MacBook with Mojave: qcocoascreen.mm:557:None(): ASSERT failure in QCocoaScreen: "The application's primary screen should always be in sync with the main display", file

[Interest] Assertions from QQuickTableView::forceLayout()

2019-09-20 Thread Patrick Stinson
TableView.forceLayout() seems prone to throwing assertions related to internal data structures being out of sync with the number of rows and columns from the QAbstractTableModel used. Some of these assertions were fixed in 5.13.0, more were fixed in 5.13.1. But this one still remains: