This question is locked. New answers and comments are not allowed.
How is one supposed to use the Template property on the GridColumnSettings<T> instances?
I could not find a way to affect the output in the grid HTML from the delegate assigned to the Template property, I am assuming there would be a way?
I assumed this property could be used to affect the html output from the Controller, just like the template column definitions can in the view. Am I wrong about that? Is intended for something else?
If so, what is the "proper" way of achieving a template column from the Controller?
Having the code helps out a lot, so I took the initiative and added my own property, "InlineTemplate" (Func<T, object>) to the GridColumnSettings<T>, which is then assiged to the GridColumnBase<T>.InlineTemplate by the GridColumnGenerator<T>.CreateBoundColumn() method. It works like a charm, and does what I expected the Template property would do, but I am hesitant to deploy this solution into production.
Is this the right way of doing it? If so, can this be integrated in the release code, so that going forward we can use the release assemblies instead of our custom builds?
I could not find a way to affect the output in the grid HTML from the delegate assigned to the Template property, I am assuming there would be a way?
I assumed this property could be used to affect the html output from the Controller, just like the template column definitions can in the view. Am I wrong about that? Is intended for something else?
If so, what is the "proper" way of achieving a template column from the Controller?
Having the code helps out a lot, so I took the initiative and added my own property, "InlineTemplate" (Func<T, object>) to the GridColumnSettings<T>, which is then assiged to the GridColumnBase<T>.InlineTemplate by the GridColumnGenerator<T>.CreateBoundColumn() method. It works like a charm, and does what I expected the Template property would do, but I am hesitant to deploy this solution into production.
Is this the right way of doing it? If so, can this be integrated in the release code, so that going forward we can use the release assemblies instead of our custom builds?