Hi Syncfusion,
I am in the process of evaluating your products as replacement for an existing components.
I am interested in creating charts from data stored on disk and importing them into a PDF file as vector images.
As the attached project will show (using random data to represent reading data from disk) I am doing this by saving my chart as an EMF file, then importing this file into a PDF document then finally saving the PDF.
I do however have a number of issue with doing this:
1.At 1601 points although the EMF file is correct, the series lines aren't imported into the PDF file. The chart is there... it just has no data.
2. Up until the point where the PDF file is saved, I cannot delete the EMF file since it is in use... this means I have to create 100 EMF files all with different file names before I can delete them again after the PDF save.
3. I cannot find a way to get the data from the chart into PDF without saving an EMF file to disk. Is there a way?
3. The process of creating a PDF file with 100 charts takes over 500Mb of RAM, is there a method for progressive file saving and releasing of RAM so as not to completely kill the processing PC? There might be circumstances where instead of 1601 points I have 16001 points and during testing my 4Gb of RAM development machine runs out!
4. When creating 100 different charts I receive this warning message:
C# effected Line: pdfDoc.Pages[i].Graphics.DrawImage(PdfImage.FromFile(file), 0, 0, 400 , 600);
Message:
ContextSwitchDeadlock was detected
Message: The CLR has been unable to transition from COM context 0x35bac0 to COM context 0x35bc30 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations.
Any assistance you can offer for these issues would be greatly appreciated and help me in my evaluation of Syncfusion's products.
Thank you
Craig.
Chart2PDF_d5f6d4c4.zip