There are many tools with which anyone can develop a working application. But after a few days the applications starts to fall apart due to the lack of the proper software designing and developing technique. Experienced developers give considerate amount of time in software designing, taking note of the system requirements, and choosing the developing pattern. This is done to make the application withstand any kind of difficulty it might face in the future and without affecting the performance. Dapfor also experienced also gives considerate amount of time on the grid performance. Giving time to the grid performance is very important because very software that has ever been developed have some kind of bugs, so it is important to have an application which has least number of problems. Many organizations applications come with lots of functionality but they lack the Dapfor’s grid performance.
The grid performance effects each and very functionality of the application. For example, updating data also have a huge effect on the grid performance. If the application uses the non-event based model then it will not implement the INotifyPropertyChanged interface. To update the data, a simple Cell.Value method is used for this purpose. This method can be invoked by any threads including that of the GUI. To save the application from the deadlock situations Control.Invoke() method is invoked which is a synchronized one. In other words, synchronize means that whenever a thread enters into a synchronized method no other thread is allowed to enter the method which avoid in changing the data. Synchronized method slows the grid performance little bit it makes the application safe. For example look at the code below which add a new object to the grid and try not to decrease the grid performance.
grid.Rows.Add(new object[]{"Unknownvalue", 123, true, DateTime.Now});
//Data is updated by calling Cell.Value property.
Row row = ...;
Cell cell = row[0] ;
cell.Value = "value2";
The grid performance also depends on various factors such as the numbers of data available on the grid. If the number of data is less than or equal to 200000 then it wont have a huge impact on the grid performance, but if the number of data is more than that it will have a negative effect on the grid performance. This is a major issue which is looked carefully into by the experienced bunch of Dapfor’s developer and tries to make sure that the grid performance is not hampered. They try to negate the effect on the grid performance. Using INotifyPropertyChanged interface also helps in improving the grid performance of the application. In such kind of scenario, Row.Update() method is invoked whenever modification of the data is required, this has good effect on the grid performance.
The grid performance effects each and very functionality of the application. For example, updating data also have a huge effect on the grid performance. If the application uses the non-event based model then it will not implement the INotifyPropertyChanged interface. To update the data, a simple Cell.Value method is used for this purpose. This method can be invoked by any threads including that of the GUI. To save the application from the deadlock situations Control.Invoke() method is invoked which is a synchronized one. In other words, synchronize means that whenever a thread enters into a synchronized method no other thread is allowed to enter the method which avoid in changing the data. Synchronized method slows the grid performance little bit it makes the application safe. For example look at the code below which add a new object to the grid and try not to decrease the grid performance.
grid.Rows.Add(new object[]{"Unknownvalue", 123, true, DateTime.Now});
//Data is updated by calling Cell.Value property.
Row row = ...;
Cell cell = row[0] ;
cell.Value = "value2";
The grid performance also depends on various factors such as the numbers of data available on the grid. If the number of data is less than or equal to 200000 then it wont have a huge impact on the grid performance, but if the number of data is more than that it will have a negative effect on the grid performance. This is a major issue which is looked carefully into by the experienced bunch of Dapfor’s developer and tries to make sure that the grid performance is not hampered. They try to negate the effect on the grid performance. Using INotifyPropertyChanged interface also helps in improving the grid performance of the application. In such kind of scenario, Row.Update() method is invoked whenever modification of the data is required, this has good effect on the grid performance.