Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311353 - Single/MultipleChoiceRidget - stays empty when used with CompositeTable
Summary: Single/MultipleChoiceRidget - stays empty when used with CompositeTable
Status: RESOLVED FIXED
Alias: None
Product: Riena
Classification: RT
Component: demo & examples (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 2.0.0.RC1   Edit
Assignee: Elias Volanakis CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-03 07:28 EDT by Christian Campo CLA
Modified: 2010-05-12 16:45 EDT (History)
1 user (show)

See Also:

Attachments
screenshot after pressing delete (48.13 KB, image/png)
2010-05-03 07:30 EDT, Christian Campo CLA 		no flags Details
screenshot after scrolling (50.32 KB, image/png)
2010-05-03 07:31 EDT, Christian Campo CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Campo CLA 2010-05-03 07:28:08 EDT 
I played around with the CompositeTable example in the example playground. When I clicked the Delete button I expected that the row I was in is deleted. Strange enough of the three columns, the two right ones are now shown empty.

Is that the intended behaviour ?
Comment 1 Christian Campo CLA 2010-05-03 07:29:45 EDT 
It seems a redraw problem. When I screen up, it shows column 2 and 3 for the first row.
Comment 2 Christian Campo CLA 2010-05-03 07:30:30 EDT 
Created attachment 166766 [details]
screenshot after pressing delete
Comment 3 Christian Campo CLA 2010-05-03 07:31:08 EDT 
Created attachment 166767 [details]
screenshot after scrolling
Comment 4 Elias Volanakis CLA 2010-05-12 14:41:32 EDT 
Reproducible. Investigating.
Comment 5 Elias Volanakis CLA 2010-05-12 16:45:46 EDT 
The cause is was a change in Multiple/SingleChoiceRidget.

LNF_UPDATER.updateUIControlsAfterBind(control); was commented at the end of createChildren(). I have reenabled it. It causes the widget to re-layout itself which is necessary after adding content.

@Thorsten: if this creates any problem for you, let me know. I believe you had commented it out with the last commit to these files.