[nebula-dev] Grid vs. Table different VIRTUAL behavior

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[nebula-dev] Grid vs. Table different VIRTUAL behavior

From: Rob Adams <robfadams@xxxxxxx>
Date: Mon, 17 Mar 2008 14:34:25 -0700
Delivered-to: nebula-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/nebula-dev>
List-help: <mailto:nebula-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/nebula-dev>, <mailto:nebula-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/nebula-dev>, <mailto:nebula-dev-request@eclipse.org?subject=unsubscribe>
User-agent: Thunderbird 1.5.0.8 (Windows/20061025)

I want to use the Grid in VIRTUAL mode for potentially huge datasets.

However, I get an out of memory error when passing large numbers (950K)to setItemCount(). It appears that Grid.setItemCount() simply createsthe given number of items, whereas Table.setItemCount() does not. Isthis a bug?

Is there any advice for handling datasets of this size with the Grid?Has anyone else had success in this type of situation?


Thanks,
Rob Adams

Follow-Ups:
- Re: [nebula-dev] Grid vs. Table different VIRTUAL behavior
  - From: Christopher J Gross

Prev by Date: [nebula-dev] Fixed header row
Next by Date: Re: [nebula-dev] Grid vs. Table different VIRTUAL behavior
Previous by thread: [nebula-dev] Fixed header row
Next by thread: Re: [nebula-dev] Grid vs. Table different VIRTUAL behavior
Index(es):
- Date
- Thread

Breadcrumbs