As we all know, RadGrid has many amaing features. But I also find that there are some things missing that feels like it should really have been there form the begining. On of these things, as far as I know, is the inability to differentiate between Updates and Inserts when it comes to editing in the RadGrid. What I mean is something simple like say a Grid with 3 columns where all 3 should be editable when you create a new record, but only 2 of them should be editable on updates (for whatever reason that might be).
This feature has been available in the Microsoft control for as long as I can remember, why is this not the case in the RadGrid? Is it just missing, or is there a good reasons for why it is not available in an easy maintainable way? There are some ways you can do this in code, but that really does seem more like a work around, rather than a really good solution to handle it. Perhaps I am a bit old fashioned, but I don't really like having to write a lot of "GUI code" for stuff that should be built in, mainly because it often gets quite hard to follow, and requires a lot of work to maintain.
So, assuming this feature isn't available and that I have just missed it, what is the best way to implement this, in a way that isn't to much of a nightmare to maintain and implement? Any why isn't it there in an easy way to begin with, I don't think that we can be the only ones with this problem?
This feature has been available in the Microsoft control for as long as I can remember, why is this not the case in the RadGrid? Is it just missing, or is there a good reasons for why it is not available in an easy maintainable way? There are some ways you can do this in code, but that really does seem more like a work around, rather than a really good solution to handle it. Perhaps I am a bit old fashioned, but I don't really like having to write a lot of "GUI code" for stuff that should be built in, mainly because it often gets quite hard to follow, and requires a lot of work to maintain.
So, assuming this feature isn't available and that I have just missed it, what is the best way to implement this, in a way that isn't to much of a nightmare to maintain and implement? Any why isn't it there in an easy way to begin with, I don't think that we can be the only ones with this problem?