What's New in iGrid

[New] When iGrid is disabled, the cell check boxes are drawn using the corresponding style that indicates that they are inactive (in the previous versions they remained the same and look clickable).

[New] The FillFromRS method now supports both DAO and ADO recordsets.

[Change] A more accurate algorithm that calculates the size of the scroll box on the iGrid scroll bars was implemented. Now the scroll box on each scroll bar correctly represents the portion of the grid that is visible in the client area in all possible cases.

[Fixed] The SelItems object might contain improper data when you access it in the BeforeSelectionChange event.

[Fixed] If you pressed a character key in a combo cell to open the drop-down list and select the first item which starts with this letter, and there was no such an item, the list remained opened after you pressed TAB.

[Fixed] The CellTypeFlags property returned improper values.

[Fixed] iGrid might scroll its contents up if you selected the last row and it was fully visible; the same effect you might see for columns and if you issued the EnsureVisibleCell, EnsureVisibleRow or EnsureVisibleCol method.

[Fixed] Some problems with displaying Unicode characters in the iGrid combo boxes.

[Fixed] The background color of a text cell could be set to an improper value while editing if you had invisible rows and the BackColorEvenRows and/or BackColorOddRows properties had non-default values.

[Fixed] The iGrid scroll bars might become "frozen" (you couldn't control them with the mouse) if you moved iGrid on a form.

[New] The previous builds of iGrid do not allow you to use such iGrid control keys as HOME, END, PAGEUP, PAGEDOWN, ENTER, ESC properly in MS Access because that development environment consider those keys as its own control keys and they simply do not reach iGrid if you press them (for instance, ENTER is used to move from one field to another, and the END key can be used to move to the last object on the form). In this build of iGrid we implemented a special new COM keyboard hook which allows you to use those keys as expected in iGrid when it has the input focus.

[Change] Many ActiveX control containers such as VB forms allow you to process form-level keystrokes if you set their KeyPreview property to True regardless of what control on the form has the input focus. In the previous versions an iGrid control key can work in iGrid and generate the form's KeyDown or KeyPress event as well if the form's KeyPreview is on. Now, if an iGrid control key can perform an action in iGrid, it is not passed to the form. For more info, read the "iGrid and the KeyPreview property in VB" topic in the updated help file.

[New] The CTRL+HOME and CTRL+END keyboard combinations allow you to move the current cell selection to the upper-left and bottom-right cell respectively (in the previous builds, these combinations are used to move the current cell to the first or last cell in the current row without changing the selection if multi-selection mode is on).

[Fixed] When iGrid was in edit mode, pressing the TAB key might trigger the KeyPress event (KeyPress can be raised only when iGrid is not in edit mode).

[Fixed] The flags which indicate the state of the ALT and CTRL keys might be passed improperly (one instead the other) in the Shift parameter of the KeyDown/KeyUp events for the TAB key.

[Fixed] The RowIsGroup and RowGroupStartCol properties could return improper values.

[Fixed] The selection of the current row might work improperly if you called the RemoveRow method with the lCount parameter greater than 1.

[Fixed] The CellDynamicText event might pass improper values in its lRow parameter.

[Fixed] Sorting by cell text (the igSortByCellTextUseCase and igSortByCellTextNoCase sort types) might work improperly if you used dynamic cell texts generated in the CellDynamicText event.

[Improved] If you work with large grids or use extensively RAM in your app, you may consume all available memory. If a statement of Visual Basic cannot be executed due to this problem, VB generates the error 7 "Out of memory" only for its native instructions. Now iGrid has its own "Out of memory" error (the code is &H8004020B) which is raised in the most typical situations when the available RAM is not required to perform a method or property of iGrid, and you can also process this error in your code to inform the user about this problem.
For more info, read a new topic named Handling the "Out of memory" Error in the help file.

[Fixed] One problem with automatic calculating of the header height when some header items were formatted using the igTextWordBreak flag was fixed.

[Fixed] iGrid might fail if you issued the ClearSelection method when iGrid was losing the focus, had invisible rows and was in edit mode (a series of "Invalid value" message boxes could be generated).

[Fixed] In Windows Vista iGrid didn't redraw a combo box cell after an item was selected from the drop-down list.

[Improved] The EnsureVisibleRow method now can be used in the situation when the vertical scroll bar is invisible.

[Fixed] After you have edited a text cell, pressing the TAB key to move to the next cell may change the next cell value to the value entered in the previous edited cell.

[Fixed] In multiselection mode SHIFT+TAB moved the current cell to the previous cell and selected this cell (because the SHIFT key was used). Now this key combination simply moves the current cell selection as if you pressed the LEFT key.

[Fixed] The height of combo items might be changed incorrectly if you had changed the font of the combo object.

[Fixed] The AutoWidthCol method might work improperly for columns with cells which stored the vbNullString values (not empty strings like ""). The width of such a column was increased by several pixels each time you called that method.

[Fixed] The RemoveCol method might not work if the grid didn't have rows.

[Fixed] If a column had cell texts with the flags igTextEndEllipsis, igTextSingleLine and igTextCenter set simultaneously, and the column was enough narrow, you could see an ellipsis in the adjacent columns.

[Fixed] iGrid might redraw its header incorrectly if you changed the width of the first column to 0 with the ColWidth property.

[Fixed] The properties of the horizontal scroll bar could be set improperly if iGrid contained frozen columns and columns with 0 width.

[Fixed] The EnsureVisible* methods might not work in some cases when the display mode of the scroll bars was set to igScrollBarDisplayNever (the DisplayMode property of the ScrollBarObject).

[Fixed] Fixed some redraw issues when the display mode of the vertical scrol bar was igScrollBarDisplayNever.

[Fixed] Fixed some problems with the AddCol method (the previous current cell might remain selected when you select a new cell; specifying a value greater than 1 for the lCount parameter might also cause an error).

[Fixed] A combo list attached to a cell might remain opened if you hit the TAB key to move the current cell selection to another cell.

[Fixed] Some problems with redrawing column header texts if you unchanged them with the ColHeaderText property when Redraw was set to False fixed.