aboutsummaryrefslogtreecommitdiffstats
path: root/src/qml/jsruntime/qv4sequenceobject.cpp
diff options
context:
space:
mode:
authorLuca Di Sera <[email protected]>2024-12-19 12:47:52 +0100
committerLuca Di Sera <[email protected]>2025-02-05 18:39:23 +0100
commit063ab57c0d20da54a3fb7ecbeac103bac9aee7da (patch)
tree7428407b4a661c71a690ce685c4272c5c64a3372 /src/qml/jsruntime/qv4sequenceobject.cpp
parent0b1b754d537aa892101d385c7f36eb5b6d8d333c (diff)
Enable read-backs for DateObject
Certain objects in V4 are `ReferenceObject`s, keeping tracks of the data they originate from and performing read/write-backs from/to it to keep the data in sync between the reference object and the original data. For example, some C++ types are converted to reference objects, so that mutations on the QML side and the C++ side are represented on both sides. `DateObject`, which implementes the Javascript `Date` object, is a `ReferenceObject` and is used, for example, to track `QTime`, `QDate` and `QDateTime` objects coming from the C++ side. While it has implemented the required infrastructure for read-backs for quite a while, it has not really made use of it in its methods, so that they would generally never consider the original data even whey they are supposed to. Thus, ensure that a `DateObject` performs a read-back in its various "getter"/"conversion" methods, when appropriate, to remain in sync with its origin. Add a series of test cases to ensure that the affected methods will now read-back as required. Change-Id: I48e841ff0f176f3ab6ab08ede999352f71297fca Reviewed-by: Fabian Kosmale <[email protected]>
Diffstat (limited to 'src/qml/jsruntime/qv4sequenceobject.cpp')
0 files changed, 0 insertions, 0 deletions