McBasic™Get McBasic™ ↗
Build 881
Hands-on tutorial · Layout & Forms

Let a container arrange its children

Use flow layout instead of maintaining every child coordinate manually.

1 Form / control designs1 complete BASIC filesGuided sample project

Flow layout is useful for a variable number of similar controls. The parent owns arrangement, so tune spacing and flow behavior before trying to compensate with child Left and Top values. Check both a wide and a narrow window.

Step 1Prepare a safe practice project#

Extract the archive into a new writable folder, separate from your own application. Open FlowLayoutPanel.mcbproj in McBasic™. Keep every declared source, layout, resource and migration file together.

To reconstruct it yourself, create a DesktopApp project and add the files declared below. In the complete project, follow these steps as a guided rebuild: replace each named source file once and Check after all its procedures are present.

Exact project configuration
project.mcproj
{
  "schemaVersion": 1,
  "projectId": "f89c276c-3529-4df5-9dcf-38b90c29de24",
  "name": "FlowLayoutPanelSample",
  "kind": "DesktopApp",
  "ai": {
    "storeChatsInProject": false
  },
  "language": {
    "dialect": "McBasic1",
    "requireExplicit": true,
    "compare": "Binary",
    "defaultArrayBase": 0
  },
  "application": {
    "bundleIdentifier": "com.mcbasic.samples.flowlayoutpanel",
    "version": "0.1.0",
    "buildNumber": "1",
    "startupFormId": "form-main",
    "shutdownMode": "OnStartupFormClosed"
  },
  "forms": [
    {
      "id": "form-main",
      "typeName": "frmMain",
      "layout": "Forms/frmMain.form.json",
      "code": "Forms/frmMain.bas"
    }
  ],
  "modules": [],
  "classes": [],
  "tests": [],
  "references": [],
  "resources": [],
  "targets": [
    "osx-arm64"
  ],
  "capabilities": []
}

Step 2Build the Form and set its properties#

frmMain

Select the Form first and set its properties. Add containers before their children. These are initial Designer values, not statements to paste into a procedure.

Form propertyValue
Caption"FlowLayoutPanel — McBasic"
Width640
Height420
MinWidth520
MinHeight340
TypeNameParent
FlowLayoutPanelflpMainForm
CommandButtoncmdFirstflpMain
CommandButtoncmdSecondflpMain
CommandButtoncmdThirdflpMain
CommandButtoncmdFourthflpMain
StatusBarstaStatusForm
CommandButtoncmdCloseForm
flpMain · exact Inspector values
PropertyValue
Left32
Top28
Width420
Height250
Padding"8"
FlowDirection"LeftToRight"
WrapContentsTrue
Spacing10
CrossAlignment"Center"
BorderStyle"Solid"
BorderWidth1
TabIndex0
Anchor edgesLeft, Right, Top, Bottom
cmdFirst · exact Inspector values
PropertyValue
Left0
Top0
Width120
Height36
Margin"2"
Caption"First"
TabIndex0
Anchor edgesLeft, Top
cmdSecond · exact Inspector values
PropertyValue
Left0
Top0
Width150
Height48
Margin"2"
Caption"Second"
TabIndex1
Anchor edgesLeft, Top
cmdThird · exact Inspector values
PropertyValue
Left0
Top0
Width120
Height36
Margin"2"
Caption"Third"
TabIndex2
Anchor edgesLeft, Top
cmdFourth · exact Inspector values
PropertyValue
Left0
Top0
Width120
Height36
Margin"2"
Caption"Fourth"
TabIndex3
Anchor edgesLeft, Top
staStatus · exact Inspector values
PropertyValue
Left32
Top330
Width420
Height26
Text"Ready"
TabIndex1
Anchor edgesLeft, Right, Bottom
cmdClose · exact Inspector values
PropertyValue
Left480
Top324
Width128
Height36
Caption"Close"
TabIndex2
Anchor edgesRight, Bottom

Step 3Connect the events explicitly#

frmMain

ObjectEventProcedureParameters
cmdCloseClickcmdClose_ClickClick()
FormLoadForm_Load()

Step 4Enter the complete behavior#

Open the named source file. Enter declarations first, then every procedure. Expand a procedure for its full body, or copy the complete file. Helpers are required: do not stop after entering the first Click handler.

Forms/frmMain.bas

Enter these declarations at file scope, before the procedures.

Forms/frmMain.bas · declarations
Option Explicit
Private Sub Form_Load()

Initialize state before enabling dependent actions. Keep the shared declarations and startup dependencies with this procedure.

Forms/frmMain.bas · Form_Load
Private Sub Form_Load()
    flpMain.FlowDirection = "LeftToRight"
    flpMain.WrapContents = True
    flpMain.Spacing = 10
    flpMain.CrossAlignment = "Center"
    staStatus.Text = "Flow layout ready"
End Sub
Private Sub cmdClose_Click()

Enter the complete action, including its input checks and calls to helper procedures.

Forms/frmMain.bas · cmdClose_Click
Private Sub cmdClose_Click()
    Unload Me
End Sub
Copy the complete Forms/frmMain.bas file

Replace the file once; do not append duplicate procedures.

Forms/frmMain.bas
Option Explicit

Private Sub Form_Load()
    flpMain.FlowDirection = "LeftToRight"
    flpMain.WrapContents = True
    flpMain.Spacing = 10
    flpMain.CrossAlignment = "Center"
    staStatus.Text = "Flow layout ready"
End Sub

Private Sub cmdClose_Click()
    Unload Me
End Sub

Step 5Keep resources and storage reproducible#

No external resource or migration files are declared. Any inline migration, seed data or local JSON is present in the code above. Runtime application data and private preferences are not included in the archive.

Step 6Check, run and test the result#

Save all files and run Check. Resolve diagnostics before Run. Developer CLI users can work from the extracted folder:

Developer CLI
mcbasic check FlowLayoutPanel.mcbproj
mcbasic run FlowLayoutPanel.mcbproj

Acceptance checklist

  • Run at the initial width.
  • Make the window narrower and inspect the children’s arrangement.
  • Navigate between the commands using Tab.

Step 7Make one change and repeat the tests#

Add another child and check that the container still arranges all items without overlap.

Save a working Git checkpoint first. Change one behavior, Check again and repeat the acceptance checklist. Compare with the downloaded solution if a regression appears.

Source baseline 20f4bfed6b · Build manifest