0.3.2 — Read-only select fields

Fixed

• A read-only Select can no longer be changed. read_only=True was accepted and then ignored: the dropdown arrow dimmed, so the field looked locked, while clicking its text area still opened the option list and let a new value be chosen. The list now stays shut from both the arrow and the field, and read_only survives being combined with searchable or allow_custom_values, which used to cancel it outright. Reading select.read_only now reports what you set — it previously answered True for every Select, whether or not one had been asked for. TimeField offers the same kind of dropdown and had the same defect on its own read_only, both when passed to the constructor and when set afterwards; a locked time field is now genuinely locked, and its time list stays shut. (#453)

What's Changed

• Let the shared-root scene reset see what a test actually builds (#407) by @israel-dryer in #450
• fix(select): read_only closes the option list (#453) by @israel-dryer in #454

Full Changelog: v0.3.1...v0.3.2