True when the user cannot edit the view.
The view's entity: its fields are the targets a property can filter.
ReadonlyOffsetThe properties being edited.
ReadonlyTokensReadonlyTypesFields a property can target: every non-binary field, in display order.
What is wrong with the properties now, each naming the property; saving is blocked while any remain.
A fixed default from what the user typed: a number for a number property, true/false for a boolean, blank for none.
A user token takes no offset, so choosing one drops it.
A new type keeps the operator only if the type allows it, and drops a fixed default.
True when the property's default is a date token, which can take an offset.
The Properties panel of the view designer: add, edit and remove a view's declared properties (name, type, description, default as a fixed value or a token with an offset, required, allow override, target field and operator). Edits are immutable: every change emits a new list through
PropertiesChange, so[(Properties)]works.