Onto your questions:
Thanks for the prompt reply. Without the documentation, I can't figure out how to integrate the 2 methods you posted above. How and where are they called? What is passed to them?
event is similar to RadGrid's ItemCreated
event but it is ExcelML
-specific. For example you can use it to access/modify the structure of the exported file (add remove rows/cells, etc), assign styles/values to cells and so on.
is exposed to allow you to define your own styles to customize the appearance of the exported file (borders, background/foreground colors, fonts, alignment and so on)
As I stated before we temporary
removed a part of the documentation as it needed a major rework.
However, ExportToExcel() is only exporting the page that is displayed, even though the IgnorePaging attribute in the ExportSettings is True.
This is not expected under normal circumstances. If you submit a runnable demo (attached to a support ticket) I will be able to debug it locally and find where the problem comes from.
Also, exporting in ExcelML throws a NullPointerException (or whatever it's called in .NET), though this also works for my static RadGrids.
I noticed that you found the answer in another forum thread. Let me know if the problem still exists.
I've spent the better part of the morning reading every thread in a search on "Export Settings" and I find a single reference made by a user replying to a Telerik tech that there are different event handlers for exporting in HTML and exporting in ExcelML. Why isn't something as fundamental as this stated somewhere by Telerik? If you guys would spend 25% of the time on documentation as you do answering questions in these fora and in the blog, you wouldn't have to be answering all these questions because we could figure the answers out for ourselves.
As I mentioned several times before, we had such documentation but we decided to rework it from scratch. The updated version will be available in the midst of December
together with the next release of RadControls for ASP.NET AJAX
. Excuse us for the inconvenience.
Poor documentation == job security?
I don't really understand the pun here :-) I already answered your criticism about the documentation. Our documentation team is currently working on much better and complete description about the supported formats.
the Telerik team