Bug 203558 - MultipageDialog API encourages memory use
Summary: MultipageDialog API encourages memory use
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: ERCP (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Gorkem Ercan CLA
QA Contact:
URL:
Whiteboard:
Keywords: plan
Depends on:
Blocks:
 
Reported: 2007-09-17 03:55 EDT by Gorkem Ercan CLA
Modified: 2021-07-15 12:17 EDT (History)
1 user (show)

See Also:

Attachments
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 Gorkem Ercan CLA 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 CLA 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 CLA 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 CLA 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.