Openening event for ContainerControl doesn't fire

Bodevinaat

I have a ContainerControl with a few controls. First one is a Combobox. I fill this ComboBox with

#Fill WeekComboBox
For I As Integer = 0 To 52
  WeekComboBox.AddItem(I.ToString())
Next

in the Opening event of the ContainerControl. I place several Containers in a Scrollbox:

#---------------------------------------------------------------
# MainScrollBox_Opening
# Adds containers to the scrollbox
#
#---------------------------------------------------------------

For i As Integer = 0 To 6
  Var Row As New UrenInvoerContainer
  Row.Left = 30
  Row.Top = 12 + i * 48
  Row.Width = 648
  Me.Add(Row)
Next

But the Opening event of the Container doesn't fire, nor does the Opening event of the controls in the Container.

rgb

Bodevinaat

Bug confirmed!
Workaround you can create method in you CC named "fakeOpening"

Sub fakeOpening()
For I As Integer = 0 To 52
  WeekComboBox.AddItem(I.ToString())
Next

and call after me.Add(row)

Var Row As New UrenInvoerContainer
  Row.Left = 30
  Row.Top = 12 + i * 48
  Row.Width = 648
  Me.Add(Row)
Row.fakeOpening()

Bodevinaat

Yes, thanks confirming.

Garry

Thanks for reporting this, it was indeed a bug.

Container controls took a snapshot of their existing children before firing their own Opening event. Consequently, controls added from that handler were not included in the opening pass, so neither the newly added ContainerControl nor its nested controls received Opening.

This has now been fixed: https://feedback.objo.dev/bug/1111

Controls added during a container’s Opening handler receive their own Opening events before the window becomes visible. Nested controls still open in child-before-parent order, and existing controls are tracked so their events are not fired twice.

The fix applies consistently to ScrollBox, ContainerControl, GroupBox, TabPanel, and PagePanel.

Bodevinaat

@Garry The Opening event for the ContainerControl works, but not for its Controls (children).

Garry

It's fixed in the next release (i.e. the release I am currently working on). The bug exists in the current public 26.8.3 build. I am working on 26.8.4 which will fix all of these issues 🙂