Re: [Pharo-dev] Bug in Spec layout?
This is a nightmare to solve :) a way to fix it is ti introduce another column for the two first widgets Ben On 09 Apr 2014, at 11:23, Martin Dias tinchod...@gmail.com wrote: Hello folks, When I evaluate in latest Pharo 3: DynamicComposableModel new instantiateModels: #( a TreeModel b TreeModel c TreeModel); openWithSpecLayout: (SpecLayout composed newColumn: [ :column | column newRow: [ :row | row newColumn: #a. row newColumn: #b. row newColumn: #c width: 80 ] ]; yourself) === Screen Shot 2014-04-09 at 11.09.38 AM.png Maybe I'm wrong: I expected that #a and #b have the same width. But it looks like the layout algorithm first splits the space half/half between #a and #b, and later it only shrinks #b to give the fixed space to #c. Should I report an issue? or specify layout in other way? Thanks, Martín
Re: [Pharo-dev] Bug in Spec layout?
I will try that, thanks Ben. Martín On Wed, Apr 9, 2014 at 11:33 AM, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote: This is a nightmare to solve :) a way to fix it is ti introduce another column for the two first widgets Ben On 09 Apr 2014, at 11:23, Martin Dias tinchod...@gmail.com wrote: Hello folks, When I evaluate in latest Pharo 3: DynamicComposableModel new instantiateModels: #( a TreeModel b TreeModel c TreeModel); openWithSpecLayout: (SpecLayout composed newColumn: [ :column | column newRow: [ :row | row newColumn: #a. row newColumn: #b. row newColumn: #c width: 80 ] ]; yourself) === Screen Shot 2014-04-09 at 11.09.38 AM.png Maybe I'm wrong: I expected that #a and #b have the same width. But it looks like the layout algorithm first splits the space half/half between #a and #b, and later it only shrinks #b to give the fixed space to #c. Should I report an issue? or specify layout in other way? Thanks, Martín
Re: [Pharo-dev] Bug in Spec layout?
Ben, Given that the number of columns is variable in my scenario... is there a way to set a fixed width to each column and display an horizontal scrollbar on bottom? You told me that's not supported by Spec, but maybe there is a way to workaround it inserting a Morph or something like that. Thanks, Martín On Wed, Apr 9, 2014 at 12:45 PM, Martin Dias tinchod...@gmail.com wrote: I will try that, thanks Ben. Martín On Wed, Apr 9, 2014 at 11:33 AM, Benjamin benjamin.vanryseghem.ph...@gmail.com wrote: This is a nightmare to solve :) a way to fix it is ti introduce another column for the two first widgets Ben On 09 Apr 2014, at 11:23, Martin Dias tinchod...@gmail.com wrote: Hello folks, When I evaluate in latest Pharo 3: DynamicComposableModel new instantiateModels: #( a TreeModel b TreeModel c TreeModel); openWithSpecLayout: (SpecLayout composed newColumn: [ :column | column newRow: [ :row | row newColumn: #a. row newColumn: #b. row newColumn: #c width: 80 ] ]; yourself) === Screen Shot 2014-04-09 at 11.09.38 AM.png Maybe I'm wrong: I expected that #a and #b have the same width. But it looks like the layout algorithm first splits the space half/half between #a and #b, and later it only shrinks #b to give the fixed space to #c. Should I report an issue? or specify layout in other way? Thanks, Martín
