5 Answers, 1 is accepted
0
Hi Philipp,
RadSpreadProcessing doesn't support the text-orientation property. We have already logged a feature request for that functionality and you can subscribe to track its status and vote for an implementation through the related public item.
Regards,
Tanya
Telerik by Progress
RadSpreadProcessing doesn't support the text-orientation property. We have already logged a feature request for that functionality and you can subscribe to track its status and vote for an implementation through the related public item.
Regards,
Tanya
Telerik by Progress
0
Philipp
Top achievements
Rank 1
Rank 1
answered on 17 Jan 2017, 11:30 AM
Why does RadSpreadProcessing throw away anything, that it does not understand? This reduces the usability of the library quite a bit.
0
Hi Philipp,
In many of the cases, a particular feature is related to different parts of the document model and keeping it in the document is not a suitable solution as it could lead to producing invalid documents containing broken relations. To guarantee that all the documents produced with RadSpreadProcessing are valid and you can open them with an application by your choice, the features in a document that are not supported are skipped while importing it.
Regards,
Tanya
Telerik by Progress
In many of the cases, a particular feature is related to different parts of the document model and keeping it in the document is not a suitable solution as it could lead to producing invalid documents containing broken relations. To guarantee that all the documents produced with RadSpreadProcessing are valid and you can open them with an application by your choice, the features in a document that are not supported are skipped while importing it.
Regards,
Tanya
Telerik by Progress
0
Philipp
Top achievements
Rank 1
Rank 1
answered on 20 Jan 2017, 02:54 PM
There should be an option for that. Is there any way to override that 'feature'? It removes way too much to be usable in any complex production environment. Also the documentation isnot very precise about that, or I just didn't see it.
0
Hi Philipp,
The behavior is not related to a particular functionality but to the implementation of the library. When you import a file using the format providers of RadSpreadProcessing, it is translated to the internal document model of the library. When the document contains features that are not supported by that model, there is no way for the import process to keep them and still allow you to edit that workbook. With that said, I am afraid that there is not much we can do at this point.
In regards to the documentation, I would like to ask you to share more information on what details you need to find there. If you think there is something missing, we will much appreciate sharing your opinion so we can improve the available information.
Regards,
Tanya
Telerik by Progress
The behavior is not related to a particular functionality but to the implementation of the library. When you import a file using the format providers of RadSpreadProcessing, it is translated to the internal document model of the library. When the document contains features that are not supported by that model, there is no way for the import process to keep them and still allow you to edit that workbook. With that said, I am afraid that there is not much we can do at this point.
In regards to the documentation, I would like to ask you to share more information on what details you need to find there. If you think there is something missing, we will much appreciate sharing your opinion so we can improve the available information.
Regards,
Tanya
Telerik by Progress