Hi dave
Moose needs OSProcess and squeaksource is unstable so I will move OSProcess (except if you want to do it) because
we should get our build stable and I should losing teim trying to build moose.
So let me know.
Stef
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Milestone-4.8
New issue 968 by usman.bh...(a)gmail.com: Update droplist presentation
selection index
http://code.google.com/p/moose-technology/issues/detail?id=968
I am trying to change dynamically selection index of a droplist in Glamour.
But changing the selectedIndex upon selection does not change anything in
the browser. Here is my code:
|browser |
browser := GLMTabulator new.
browser row: #one size: 30; row: #two.
browser transmit to: #one; andShow: [:a |
a dropDownList
display: [:x | 1 to: 12 ];
selectedIndex: 10 ].
browser transmit from: #one; to: #two; andShow: [:a |
a list
display: [:x | 1 to: x ];
selectionAct: [:aPres :each | (browser paneNamed: #one) presentations
first selectedIndex: 1] entitled: 'select in dropList'
].
browser openOn: 1
Populating the pane port with the selected does change the list items but
it does not update the selected value in the dropdown list.
selectionAct: [:aPres :each | ((browser paneNamed: #one) port: #selection)
value: (1)] entitled: 'select in dropList'
].
Could you suggest how can I update droplist and the list upon the change of
selectedIndex?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Hi,
I will soon need to analyze quite some java code at once and I'm already
sure that one Moose image will not be enough for all that code. Therefore I
would like to try to persist the model on a database. Do you have any
pointer to a possible persistence manager/OODBMS/RODBMS to use for that
purpose?
Thanks in advance,
Fabrizio
ROUnhighlightElement and ROHighlightElement classes have been removed from
Roassal so GLMBasicExamples>>roassalWithCustomHighlight should be changed.
Here is the fix that works:
| browser |
browser := GLMTabulator new .
browser
with: [:tabulator |
tabulator column: #index; column: #visualization.
tabulator transmit to: #index; andShow: [:a | a list ].
tabulator transmit to: #visualization; andShowIfNone:[ :a |
a roassal
painting: [:view :collection :roassal |
view shape label.
view interaction on: ROMouseLeftClick do: [:ann | (roassal pane port:
#selection) value: ann element model ].
view nodes: collection.
view gridLayout.
roassal on: GLMContextChanged do: [:ann |
ann property = #selection ifTrue: [
ann oldValue ifNotNil: [
ROBlink unhighlight: (ann presentation view raw elementFromModel: ann
oldValue).
ROBlink
highlight: (ann presentation view raw elementFromModel: ann value)
].
]]]].
tabulator transmit from: #index; to: #visualization port: #selection.
tabulator transmit from: #visualization port: #selection; to: #index port:
#selection.
].
browser openOn: (1 to: 42)
Hi,
In order to start the organization of the MooseDay in Lille, we would like to know, who would be interested in attending and who would like to make a presentation. The idea would be to organize it the first or the second week of October.
Please let us know your interest in the MooseDay in Lille (France).
Thanks in advance.
Anne
Hi Fabrizio,
Moose models are highly interconnected, and the analyzing algorithms tend to touch
a lot of other objects. There is very limited locality of reference, so a RDBMS (or NoSQL)
cannot help you here. You basically would only be swapping in and out objects.
Stephan