Documentation of IgnoreParentReadOnly is confusing

[henrique]

Hi!

I'm reading the documentation about the config called IgnoreParentReadOnly, but the text is a little confusing. For me, if the config is setting to "True", the widget will not be read-only if the parent is, and if the config is "False", the widget will be read-only if the parent is read-only, correct?

[Animal]

It's the opposite.

Setting IgnoreParentReadOnly to true, will make the widget to ignore parent's readOnly state.

It seems quite self explanatory to me.

readOnly usually cascades down.

So if you set a Container to readOnly, any fields in it will become readOnly

That allows some field to opt out of that, by ignoring the parent setting

[henrique]

I agree, but the documentation is written like this:

Determines if the widgets read-only state should be controlled by its parent.

When set to false, setting a parent container to read-only will not affect the widget. When set to true, it will.

[khattakdev]

Hey henrique,

Thanks for pointing it. We will update the docs.