Hi,

I believe the Grid sorts based on the cell values. So if the value are numbers, it sorts based on the numeric values, for example, "2" is less than "10". If the value are strings, it sorts based on the string values, in this case, "2" is greater than "10".

Thanks

Hi,

I hate to say this....but we'd much appreciated if you can check the documentation first. Our documentation is generated from the source code, so if there is something available, it will be there; otherwise there is not. Because you are feeding the Grid data, you can always sort it anyway you wanted in your datasource. The Grid does what it does and it certainly won't do everything you wanted it to do. But it is our intention that you will be able to extend it as much as possible. I believe you have pretty exploited all the major features of our Grid, so features like this are mostly likely to be implemented by yourself on your end.

Thanks

Hi,

No need to apologize. We certainly understand that you have some quick questions and it is our goal to provide you the answer as fast as possible so that you can get the most of our product, as we have been doing all along. However please be rest assured that we response a question, we don’t tell you half and hold the other half. So if you turned the stone and nothing shows up, then there is nothing there. :) Sorry about that!

While it is not possible for us to include every feature that you would like to have due to the fact that we have to balance between features, size, flexibility, usability and different user opinions, we always try to leave the door open for you to extend it to fit your own specific needs ---- as you have experienced in the case of CustomColumn and ColumnSort event for sorting. You will find many cases echo this design philosophy through out our product. That’s why we though it’s important that you understand you can play a significant part as well. We hope you find such interfaces useful.

As explained earlier, our documentation is generated from the source code, so it's a complete reference of what's available. So when you have a question, it's always a good idea to check the documentation first. That way you will get the answer instantly, instead of having to wait for us to response. As you use our support more, you will find out that most of our support works cover things that are included in the documentation, but are not as obvious ---- such as you can put a drop down box on the column header with HTML code. That once again highlights the design philosophy mentioned above.

So if you still have questions that you feel is within the set framework of the Grid, please feel free to ask and we will try our best to give you an accurate answer; Or you can post a feature request about something that you don’t see but feel it would make sense to have. We will also do our best to accommodate that. Since you are already pretty much a guru of our Grid now, we do not expect to be able to provide you much new information. That's also why we thought for many features that you do not find in our documentation, you will need to implement them by yourself. The good thing is that we have put in considerable effort when designing the product so that such customization/extension is not only possible, but easy enough for most users.

Hope this helps you to make an informed decision.

Thanks

Glad to hear that and thanks for understanding!