> For the complete documentation index, see [llms.txt](https://able.bucca.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://able.bucca.com/core/overview/radiobutton/radiobutton-shape.md).

# Ω RadioBtnShape

Base: The shape given to a radio button and its status at the Primitive level.

[Styleguide Link](https://zpl.io/V0rdg0E)

Parent: [RadioBtnCtrl](/core/overview/radiobutton.md)

To start with we will have two shapes available, the default normal round [radio button](https://zpl.io/V0rdg0E) (that you see most of the time) and a customized appearance of "[Circle Check](https://zpl.io/anBGkKv)". These "Shapes" are set in the child level area of "Base - Shape" for the parent Radio Button Primitive.

The appearance of the shapes and status (on, off) are supplied from an icon in the icon library (Icons-Base > Icons > Primatives). They are labeled in the icons file as Radio On/Off for the squared off and Selection On/Off for the circular checkbox. Note, this is the same icon file used for the customized Checkbox version as well.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://able.bucca.com/core/overview/radiobutton/radiobutton-shape.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.