Guide 02 · Designer

Design the interface, then define behavior

The visual designer is for arranging an application's user interface. Python code supplies the application logic. Both sides should be reviewed together whenever an event or property changes.

01 / STRUCTURE

Forms and containers

Start with a form as the window for your application, then place controls inside it.

02 / DISCOVERY

Toolbox and components

Use the Toolbox to see what is actually available in the current IDE build.

03 / CONFIGURE

Property editor

Edit exposed properties and check the resulting appearance in the preview or running application.

04 / REACT

Event handlers

Attach actions such as click or change events to Python logic; test each interaction in a running project.

A practical first exercise

Build a small form with a label, text input, and button. Run it and confirm that clicking the button produces the expected result. Once it works, try resizing the form and changing a property to understand how the designer affects application behavior.

Designer and runtime are separate verification steps.

A control that looks correct in the designer still needs to be tested in the executed application and, when relevant, in the published Windows executable.

Advanced components

Visual Python Studio development includes data-oriented, graphical, analytical and automation-related components. Reference pages will identify supported properties, events, dependencies and limitations individually rather than imply that every planned component is already release-ready.

Documentation status

This material explains the workflow and current development direction. Exact menu labels, Python APIs and compatibility details will be checked against the public release and identified by version.

← All documentation