This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
We noticed something different after updating our version of the Mindscape WPF DataGrid controls. We have a datagrid where the user is able to add rows automatically at the bottom. Normally there is one row for the user to enter data. However, with the latest version of Mindscape WPF Elements our Data Grid has two blank rows at the bottom. This is confusing some of our users. Is there a way to set the style to the previous functionality? I've attached a snapshot of the Mindscape WPF Elements AllowUsersToAddRows sample, showing the two blank rows at the bottom to help explain what I'm talking about. |
|
|
|
|
Hi, Unfortunately I have not been able to reproduce 2 blank rows appearing at the bottom of the DataGrid. Did you reproduce this simply by running up the AllowUsersToAddRows sample? If not, please send me a simple repro project demonstrating the issue. -Jason Fauchelle |
|
|
|
|
That's correct - running directly from [C:\Program Files (x86)\Mindscape\WPF Elements\Samples] without touching the sample source code files in any way - We are using version 7.0.34.23280 Our version also puts two empty rows at the bottom of the grid in our custom solution which references the DLL. (Which is where we first noticed it) Is this perhaps a known issue with the version of the assembly we are using? After researching further older builds of our solution running with an older version of the WPF data grid did not have two blank rows at the bottom, which is why some users had been confused by the change - although it's taken several months for the defect to reach me here in development.... ;) |
|
|
|
|
Hi, Thanks for the additional information. I have tracked this down and remember now that this was an issue around the version number you posted. This issue was resolved several versions later. You'll want to get the latest version, or use an older version that you have in order to rid this issue. -Jason Fauchelle |
|
|
|
