The following table lists the changes in TEdit.NET version 2.5.1467. Users
of previous versions are advised to upgrade to the latest version.
|
Change |
Description |
| Support for blank primary key |
In case a row in a table contains a primary key that is an empty (blank)
string, clicking the Edit button for that row failed. This is now fixed.
|
The following table lists the changes in TEdit.NET version 2.5.1466.
|
Change |
Description |
| Fix for AutoRowSelect |
Fixed a bug related to the AutoRowSelect feature. If AutoRowSelect was enabled,
an error could occur when manually creating a master/detail relation between
two table editors by handling the RowSelected event. When handling the
RowSelected event, a call to Rebind() could fail with the error Rebind()
cannot be called at this time as ASP.NET PostBack data is not yet loaded.
The problem did occur in the
stored procedure sample.
|
| RowSelected event improved |
Improved the RowSelected event, so that it now also fires immediately after a
row has been added, as well as when a new row is auto-selected after a delete
operation.
|
| MaxCacheAge property default changed
|
The MaxCacheAge property
is now set to a default of 1 minute; previously, the default value was
infinite. This prevents very old data from being displayed if the data in the
underlying database table is changed. To ensure the most current data is always
displayed, disable caching by setting the IsCacheEnabled property to False.
|
The following table lists the changes in TEdit.NET version 2.5.1459.
|
Change |
Description |
| Search All resets to first page |
The Search All button now resets the grid to display the first page. |
| Pressing Enter applies new search Text |
After typing a search text, pressing Enter instead of clicking on the Search
button, sometimes caused the new search text to be ignored by TEdit.
This is now fixed.
|
| MaxCacheAge property
|
The new MaxCacheAge
property can be used to specify the time span after which the data cache is
automatically invalidated.
|
| License checking
|
After installing a license, it is no longer necessary to restart the web
server.
|
Changes in version 2.5.1428.
|
Change |
Description |
| Fix for screen refresh issue |
This release contains a work-around for a screen-layout bug in
Microsoft Internet Explorer. In some circumstances, the screen would not
repaint correctly after the Edit button of a row was clicked. The user had to
move the mouse pointer before the screen was refreshed. This issue could been
seen in the following scenario:
-
The ASP.NET Smart Navigation feature is enabled
-
The TEdit.NET control is placed on a page that is part of a frame-set
-
A bitmap image is used for the edit button.
After a click on the edit-image, the screen would only refresh after the mouse
pointer was moved away from the image.
|
The following table lists the changes in TEdit.NET version 2.5 since
version 2.0.1272.
|
Feature |
Description |
| A New Name |
Not really a feature (or is it?): The DVXP Table Editor changed
its name to TEdit.NET! We think this change helps to differentiate between
DVXP (the company) and TEdit.NET: the
data-table editor control for ASP.NET. |
| Improved performance |
The new
IsCacheEnabled property toggles the new data caching feature that reduces
the load on the database server and improves speed significantly by keeping a
copy of the most current data in the ASP.NET cache. The caching feature is
enabled by default. The performance of TEdit.NET is also improved by various
code optimizations. And last but not least, the amount of viewstate generated
by TEdit.NET is reduced even more. |
| Direct Dataset Editing |
The new events
ProvideDataView,
ProvideLookupData and
SaveData allow binding TEdit.NET to any ADO.NET Dataset. This makes it
possible to utilize TEdit.NET for editing data from any data source or XML
file. |
| Select button ordering |
The selectButton elements in the configuration
file now allow for custom ordering of both the selection and edit buttons
to the right or left hand side of the grid. |
| Edit-in-Grid mode |
The new property
EditInGridMode allows for displaying the edit controls inline with the
grid cells |
| Enhanced support for display styles |
Each column defined in the configuration file
can now have it's own CSS class and CSS style, using the new cssStyle and
cssClass attributes in the column element.
The new properties CssClassGrid
and CssClassGridPager
of the TableEditor control allow specifying the CSS class for the HTML table
that represents the grid, and the table cell that holds the pager information |
| Customizable error handling |
The new Error
event allows for customizing the way errors are handled and displayed. |
| Custom aggregations |
The new GridDataBind
event allows access to the data that is being displayed by the grid. This makes
it possible to calculate and display summary values without having to execute a
separate database query. |
| Compound keys in master detail bindings |
It is now possible to create a master/detail table editor binding
using more than one primary key field and parameter. Each column and parameter
name must be separated by a ‘;’-character. This enables you to create a
master/detail page bound to multiple columns without having write program code. |
| Enhanced support for localization |
In addition to the existing translatable text properties, support
has been added for the error captions (TextUpdateError,
TextAddError,
TextDeleteError and
TextSearchError). |
| Added support for validators |
ASP.NET Validation controls can now be bound to controls created
by the CreateEditControl
event. |
| Minor fixes |
-
Added Quote Prefix/suffix support (in the settings element of the
configuration file)
-
Fixed a problem that occurred when changing the
ConfigFilePath at runtime after the user had changed the sort order
-
Pressing Add New while in edit mode now always saves the changes (Add New
after a previous Add New did save changes, but Add New after an click on Edit
did not)
-
Fixed a problem related to nullable bit-columns
-
In a bound master/detail editor, the default value specified for parameters is
now used when no current row is selected in the master editor, preventing
problems where an empty parameter value would generate an invalid SQL
statement.
-
Fixed a problem causing the
RowSelected
event to be fired too often
-
Fixed a problem that caused ASP.NET trace output to fail due to a duplicate
control ID
-
Fix a tab ordering problem that occurred with multiple Table Editors on a
single page.
|