Sorry, I did not pay attention and I only answered to alex Here was the answer:
I think that here you should specify something like:
lastPane addPart: part2 associatedTo: #selectedVersions requiring: #selectedConfiguration2.
Like that the input of the MultiSelectionItemSelectorPart get populated with output of the dropListPart. That means that the line:
part2 := MultiSelectionItemSelectorPart new initialList: ([:input | {input at: #selectedConfiguration2}]).
will work corectly.
Now, like andre said, this is possible that this mechanism does not work well for MultiSelectionItemSelectorPart
I can have a look today
2011/10/18 Andre Hora andrehoraa@gmail.com
On Tue, Oct 18, 2011 at 8:14 AM, Stéphane Ducasse < stephane.ducasse@inria.fr> wrote:
Are you sure that you cannot get the result of the previous pane? Because it looks strange to me.
Yes, you can in some Parts. You can check the examples #multiSelectionItemsSelectorPartUsing: #itemsSelectorPartUsing: #parametrizedChexboxesUsing: #parametrizedDropListsUsing:. The problem is that is not implemented for MultiSelectionItemSelectorPart.
Stef
On Oct 18, 2011, at 4:45 AM, Johan Fabry wrote:
Hi Alex.
I had similar problems for AspectMaps and was also surprised that Merlin
did not have built-in flow of data between different panes. So I built a hack. What I do is to initialize the second pane with dummy data, and then have a callback of the first pane replace the dummy data with real data. The code that does this is below:
AspectMapsUI >>importWizard
"Second pane contents is actually built using callback of first
pane"
"Third pane contents is actually built using callback of second
pane"
| wizard aiPane psPane javaPane resultPane labelPart filePart
importConfigs |
wizard := WizardControl new. importConfigs := OrderedCollection new. " == aspect info pane == " aiPane := WizardFirstPane named: 'Please choose a .xcr aspect
file.'.
filePart := (ChooseFilePart new) validExtensions: #(xcr). filePart callback: [:fileName | self projectSelectFrom: fileName forWizard: wizard
andConfig: importConfigs ].
aiPane row: filePart associatedTo: #aspectInfoFile. wizard addPane: aiPane. "== project select pane ==" psPane := WizardMiddlePane named: 'Please select which projects to
import'.
psPane row: (LabelPart on: 'This will be removed by the
callback').
wizard addPane: psPane. "== java source select pane ==" javaPane := WizardMiddlePane named: 'Please provide Java data'. javaPane row: (LabelPart on: 'This will be removed by the
callback').
wizard addPane: javaPane. " == last pane with report of what will be done == " resultPane := WizardLastPane named: 'Will Import'. javaPane row: (LabelPart on: 'This will be removed by the
callback').
wizard addPane: resultPane. wizard atEndDo: [ :outDict | self importProjects: importConfigs
aspects: (outDict at: #aspectInfoFile) ]; open
On 17 Oct 2011, at 10:50, Alexandre Bergel wrote:
Hi!
I am building a wizard and I am stopped on something that looks
trivial.
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry jfabry@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Andre Hora
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev