wxSmith, Sizers.

[bdad]

Codeblocks, wxSmith, layout (sizers)

In wxFlexGridSizer, there are a couple of blank fields, Growable cols and Growable rows. There are no associated check boxes or greyed out values. What could be entered there?

Is it at all possible to change a sizer type, without destroying whatever else was added after the sizer assigned?

[BlueHazzard]

My workflow was to add a new sizer and then move the "parent" sizer with all its childs to the new sizer... If you can not reuse the old sizer you have to drag and drop all the controls by hand...

[bdad]

Thanks, I'll try that. I was hoping that a text search and replace over the whole project would do it, but I can see problems in that I believe that the original sizer/position/other settings for the components within it would also need to be altered. Any idea wrt the blank Growable' fields?

[Miguel Gimenez]

The growable fields are comma-separated lists of rows or columns that can have a different size. See the control docs in the wxWidgets site.

(The separator may be space or semicolon instead, I can not check ATM.)

[bdad]

The growable fields are comma-separated lists of rows or columns that can have a different size. See the control docs in the wxWidgets site.

Thanks, I'll try and find the control docs.

[bdad]

It happens that in the WxSmith tutorial 6, that it mentions putting '0,1' into the growable property, (I've only just come across that) but when adding the subsequent panel, then codeblocks crashes. I guess it may have changed since the tutorial was last updated. I'll check the WxWidgets docs.

[Miguel Gimenez]

I can confirm it is a comma-separated list, in fact I have just added tooltips for those fields in trunk.

The problem in 20.03 arises when you write a growable column (or row) number greater or equal than the number of columns. This is fixed in trunk.

The workaround is setting the number of columns before writing the list of growable columns or using the last nightly.

[bdad]

Thanks for the further info., perhaps you can confirm what this means, (tutorial 6)

... , a wxFlexGrid Sizer with two columns, both growable.(In the Growable property of the sizer, put"0,1"without the quote marks..)

There are two fields, 'Growable cols' and 'Growable rows', the way the tutorial is worded, it is not clear if you put the '0,1', in one or both fields., afaik there is not a field labeled 'Growable property',
anyway it still crashes. Did this work previously, maybe 5 or 6 years ago, when the tutorials were written, or is there a difference in platform it is run on, or do the folk who write the tutorials not have any reviewing process?

From the wxWidgets documentation, I found

void wxFlexGridSizer::AddGrowableRow    (    size_t     idx,
      int     proportion = 0
   )       

The first digit in the tutorial is 0, meaning the first row/column, which is within the range of the two column sizer, but the second is a 1 which afaik means unequal sizing. which should not be a problem.

It may be best to download a recent nightly build, as you say, but with my luck...


Or, does it mean that the '1,0' is a list of rows/columns to be altered, and the tutorial should have said '... in the growable cols field, enter '0,1' to allow both columns to be grown,...'

[Miguel Gimenez]

the tutorial should have said '... in the growable cols field, enter '0,1' to allow both columns to be grown,...'

Correct.

wxSmith calls AddGrowableCol() for each item in the list, if any item is not a valid column index wxWidgets will show an alert. The default wxFlexGridSizer has 3 columns and 0 rows, so you can not write in the GrowableRows field until the number of rows is non-zero.

[bdad]

Yes, that worked fine. Thanks for explaining. What I found in the wxWidget documents, was not quite the explanation for filling in the fields, but I worked out what it meant, thanks to your reply, just after I posted (and b4 I edited).
It'll take me awhile to get used to the sizers, not so much in what they do, but selecting them with the mouse, in particular when starting, the frame becomes a small dot once the panel and sizers are added, then when adding a component, 50/50 chance where they  go, but can use the buttons down the rhs.  Shame not possible to put in sizers to sort out the layout after components placed.

[Miguel Gimenez]

I have just edited the tutorial to clarify what field must be edited. You can also do that with your forum user account.

[bdad]

I'm not sure if I would be capable of editing the tutorials, but I may attempt to rewrite one or two, and perhaps ask someone to review it, in order to make the tutorials  less dependent on dates, etc. In one it refers to the wxPanel component being fourth from left, the illustration shows it as fifth, in reality it is now, or was when I installed wxWidgets, the eighteenth. Also, probably because I'm building statically, I have to add in some extra header files, which could be worth mentioning.

[stahta01]

Also, probably because I'm building statically, I have to add in some extra header files, which could be worth mentioning.

It is common to have to add extra libraries when using an static wxWidgets build; but, I never had to add extra headers because of static build. But, I have not really used wxSmith very much.

Tim S.