Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 203558

Summary:	MultipageDialog API encourages memory use
Product:	z_Archived	Reporter:	Gorkem Ercan <gorkem.ercan>
Component:	ERCP	Assignee:	Gorkem Ercan <gorkem.ercan>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	rogalski
Version:	unspecified	Keywords:	plan
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:

Description Gorkem Ercan

2007-09-17 03:55:24 EDT

Current MultipageDialog API encourages the creation of all the pages. Creating the pages early consumes a memory. API should add a callback mechanism for creating the pages.

Comment 1 Gorkem Ercan

2007-11-26 04:12:58 EST

I think we should start supporting the SWT.VIRTUAL for MultipageDialog, Tree, Table and ListBox. The same memory constraints are true for all these widgets and we should resolve all at once.

Comment 2 Mark Rogalski

2007-11-28 12:42:44 EST

+1

I assume the developer using this for MPD, would still create pages up front since the titles for the tabs must still be established. But he would not populate the resulting composite until receiving a callback on a listener. The MPD then has to ensure the page widgets get displayed.

Comment 3 Gorkem Ercan

2008-01-16 08:40:58 EST

Tree and Table specification are updated to include SWT.VIRTUAL style in the specification and the setItemCount method.
TreeItem now has the setItemCount as well.
MultipageDialog spec now includes VIRTUAL style and SetData as supported event type.