iGrid as an Editable FlexGrid Replacement
Main problems of FlexGrid
The Microsoft FlexGrid control (MSFlexGrid/MSHFlexGrid) shipped with Visual Basic is enough good as a component to represent read-only tabular data for your users, but what if you want to edit them, especially if they are Unicode strings?
The next main problem of FlexGrid you may already know about is bad speed when you populate it with data, especially if you need to have a grid with thousands of rows.
Add to this a poor set of events you cannot use to control all the aspects of the grid.
And the last, but not least in the modern dynamic world, is the unchangeable old-fashioned 3D look. FlexGrid isn't supported anymore, and it cannot use all the benefits of the new visual styles available in Windows XP and newer systems. If you use FlexGrid, you lose as you have a look inconsistent with the user's OS.
If you replaced FlexGrid with iGrid
Now look at what you could do with iGrid and how it could look in Windows Vista if you replaced FlexGrid with it:
 (Click to Enlarge)Let's note just a few advantages you get when using iGrid instead of FlexGrid:
You can edit the cells using such built-in editors as text edit, combobox (drop-down list) and check box control.
The cells can store values of any type (they have the Variant type).
If a cell or column header is truncated, a built-in tooltip displays the full text.
iGrid fully supports Unicode while displaying and editing data.
The selection can be semi-transparent; row selection mode to select whole rows is also available.
The user can sort and group columns using the standard grid interface without your efforts to code this!
Discover more iGrid's advantages in the Control Tour »
|