Button control: a control that renders its items as a grid of tiles
B
Belinda Bailey
Displayr's controls are all form fields — combo box, list box, text box. There's no way to present a selection as a grid of clickable tiles, which is the standard way to offer a small set of choices on a dashboard landing page.
This should be a control, not a visualization. A visualization can't hold state, so a tile grid built as one can't filter anything — the click has nowhere to go. As a control, it inherits everything that already works: it holds a value, R can read it, and it can drive a filter.
What it would need:
Items from a variable's categories or a list, laid out vertically, horizontally, or as a grid of rows and columns. An optional second line per tile showing a value from the data, beneath the item label
An optional icon or image per tile
Per-tile accent color, and formatting for the selected, hover, and unselected states
Fixed tile size or fit-to-space
Power BI ships this as the button slicer, generally available, with this exact feature set, including grid layout, per-button images, and "highlight labels" showing a value below the button text. Its nearest Displayr equivalent is a combo box.