## Component Notes

### Designer Selections

Not all controls behave equally well to the mouse events that the Designer binds.
To select a control that does not respond to mouse clicks, go the the Objs page in the inspector and select the control from the tree.

### Spesific component notes

Here are some guidelines and gotchas of using certain components:

wxSplitterWindow | Drop the controls that you want to split inside the wxSplitterWindow. Connect the Window1 property to the first control and the Window2 property to the second. Change the SplitMode property if necessary. To select a wxSplitterWindow that already have it's windows split, click on the splitter line. Do not try to only set the second window, this is illegal in wxWidgets.
wxNotebook | Double click on the wxNotebook to bring up the Collection Editor for the notebook. If there are already pages in the notebook, double click on the page tabs. Use the collection editor to add new pages. Double click on an item to make the page the active page in the notebook. Areas indicated with a dashed red pattern indicate that they must be given a control or they will generate invalid source code. Select a control as usual from the Palette and click on the red dashed area to create.
wxStaticBox | MSW: Repaint problems. GTK: Does not respond correctly to designer mouse events, select from Objs page.
wxGrid | You have to manually add a call to either CreateGrid otr SetTable in your code after the call to _init_ctrls. See Examples/wxGrid.py
wxSlider | When used with the wxSL_LABELS style, the slider has conflicting GetPosition/SetPosition behaviour causing problems with selection in the Designer. Use not supported.
wxListBox | GTK: Does not respond correctly to designer mouse events, select from Objs page.
wxCheckListBox | GTK: Does not respond correctly to designer mouse events, select from Objs page.
wxRadioBox | GTK: Does not respond correctly to designer mouse events, select from Objs page.
wxStaticText | GTK: Does not respond correctly to designer mouse events, select from Objs page.
wxDynamicSashWindow | GTK: Does not respond correctly to designer mouse events, select from Objs page.
wxToolBar, wxMenuBar, wxStatusBar | Remember to connect these components to your Frame object with it's ToolBar, MenuBar and StatusBar properties. MSW: If a wxMenuBar is connected to the frame, the wxFrame is not selected when the Designer is opened (wxMenuBar sends a size event that interrupt the Designer) Just select it manually.

Here are some guidelines and gotchas of certain properties:

Bitmaps | The path is stored in absolute form by default. You may change this under Preferences->General->Code generation->cgAbsoluteImagePaths

Boa Constructor - Application Help - Component Notes