Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

generalise delegate property logic #61

Open
whoozle opened this issue Jun 30, 2017 · 0 comments
Open

generalise delegate property logic #61

whoozle opened this issue Jun 30, 2017 · 0 comments
Assignees

Comments

@whoozle
Copy link
Collaborator

whoozle commented Jun 30, 2017

Presumably by adding some special property type, e.g.

property generator delegate;

Remove all name-hacks

@whoozle whoozle self-assigned this Jun 30, 2017
whoozle added a commit that referenced this issue Jul 5, 2022
`model` is special - it holds delegate specific model data piece,
and at the same time it's used in views to hold ListModel instance.

At the time of the lookup, we can't say it's delegate or a property.

For instance:
```
delegate: Item { property var row: model; }
```
is been (correctly - by definition of lookup_parent) resolved as parent.model (where parent = ListView) and
model ends up being ListView.model instance, instead of model row.
Although it could be possible to figure out after #61.

See also PR #207, issue #501 and `model_row.qml` for details.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant