Skip to content
Verified Commit 9c567824 authored by ivan tkachenko's avatar ivan tkachenko 🗯
Browse files

QML: Drop all custom properties from delegate, require model object instead

The approach to copy all the model roles to custom properties clearly
was a mess, and tend to only get worse over time. Not only we had to
introduce few new ones, but none of them was marked as readonly either,
and it wouldn't support writing back to a model (through setData)
should we ever consider switching to that.

(cherry picked from commit affbf7a9)
parent f86c49e4
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment