Master UI Component, Page, Window & Mouse Pointer Properties with Naming Tips
This guide explains the key component, page, window, and mouse pointer properties in UI design, covering scroll settings, opacity handling, naming conventions for objects and attributes, and best practices for consistent, case‑insensitive usage across dynamic panels.
Component Properties
scrollX and scrollY are numeric properties that control the horizontal and vertical offset of a dynamic panel’s content. Setting scrollX moves the panel’s viewport to the specified pixel position on the X‑axis; scrollY does the same on the Y‑axis. These properties are useful for programmatically scrolling panels during interactions.
Opacity is a value between 0 (fully transparent) and 1 (fully opaque) that applies to the component’s own style. It does not affect the alpha channel of a fill colour; the fill’s opacity must be set separately if needed.
Object names are conventionally capitalised (e.g., This, Target, Window).
Object attributes start with a lowercase letter (e.g., text, name).
Variable and function identifiers are case‑insensitive in the runtime, but following standard camelCase or PascalCase improves readability.
Page Properties
Page‑level properties are typically used to store metadata such as breadcrumb navigation strings, page titles, or custom data that must be accessed by multiple widgets on the same page.
Additional example image showing a typical page‑property table:
Window Properties
Window properties expose information about the current browser window or application container, such as width, height, scroll position, and focus state. They can be read or modified to adapt UI layout dynamically.
Mouse Pointer Properties
Mouse pointer properties describe the current cursor state, including its X/Y coordinates, visibility, and style (e.g., arrow, hand, custom image). These can be used to implement custom hover effects or drag‑and‑drop logic.
AI Software Product Manager
Daily updates of Xiaomi's latest AI internal materials
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
