When we attempt to use the Table.MergeCells function for a PowerPoint presentation, it takes an average of 0.95 seconds to execute. The product is being used in a web application, so the function is unusable in its current state.
Is it possible that you're suppressing an error in a try-catch loop in your code? Catching errors is notorious for slowing down function execution. (And I can think of few other viable reasons why a slowdown of this scale would be happening otherwise.)
Just tested with table 5x4:
Merging started: 15:41:43.781
Merging finished: 15:41:43.812
So it took only 0.031 seconds.
How you tested it? In the VS debugger?
Can you send me example of your table and code you use?
Merging code doesn’t have any try-catch at all.
Probably I can increase speed in two times after some optimizations but I think your executing time is wrong.
This has not yet been fixed.
Try with a 40x30 table instead.
The merge function seems to depend on the size of the table, which is just horrible.
Hello,
We worked with tables optimization and it works much quicker now. The main problem is 40x30 table contains more than 4000 shapes and size of all these shapes should be recalculated after changing any cell. The bottleneck is not Aspose.Slides but .NET’s text processing especially Graphics.MeasureString method. Anyway, we will try to do additional optimization.
Is there any particular reason for not having a StartEdit/StopEdit pattern, like most grids have to avoid the exact same problem?
We have it and use internally for all long operations (like cells merging and many other). After small update, I think we can make it available for public use.
Can I have a time horizont please?
Is this function already in code? In which case, can I call it via reflection?