> 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/rating/ratepoint.md). # Φ RatePoint Primitive: A single point of a ratings (element) with its possible status. [Styleguide Link](https://zpl.io/VQJrR84) * Parent: [RatingCtrl](/core/overview/rating.md) * Child: [RatePointShape](/core/overview/rating/ratepoint-shape.md) ### Properties **Status** - The value given to the screen object, in this case a single step point inside of a series of steps (stepper) with status possibilities of On or Off. **Style** - Supplied by the child level (Base - Shape) this is the general appearance of the screen object. For now we have two styles, the default star appearance of a single rate point, and a heart which is our customized appearance for a single step point. Note: Additional appearance can be added to the Base - Shape file (ie. diamond, tomato "rotten tomatoes style") to extend the styles at this level. ### Interaction Rate Points act as a visual indicator of a rating as well as the point of interaction to provide a rating. A slide of the finger along multiple Rate Points will activate each of those that are rolled over in the series of rate points (Rating). So for example, if the finger starts at Rate Point 1 (far left) and is held and drug to Rate Point 4, 1-4 will have a status of On and Rate Point 5 will have a status of Off. Now lets say you start the finger at 4 and move down to 2, then only the first two Rate Points would be On and the remaining 3 Off. --- # 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/rating/ratepoint.md?ask=&goal= ``` `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.