{"version":"2.1.281","anchor":"plugin-ui-held-element-presses-can-reject-values","canonical_anchor":"plugin-ui-held-element-presses-can-reject-values","heading":"Plugin UI: held element presses can reject values","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/plugin-ui-held-element-presses-can-reject-values","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Plugin UI: held element presses can reject values\n\nPlugin UI elements can now refuse a value when pressed and held, and ui.render runs inside a drawing context\n\n**Unclear.** The finding does not say what running `ui.render` inside a drawing context changes for plugin authors.\n\n**What**\n\nPlugins can draw their own interface elements. When one of these elements is pressed and held, the plugin can now check the value and refuse it, in which case the message is that it does not take that value and nothing ran. These events can also carry a request ID. `ui.render` now runs inside a drawing context.\n\n**Why**\n\nA refused value now ends with a clear statement that nothing ran, rather than the element acting on input it cannot use.\n\n- Area: Plugins\n- Names: `ui.render`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}