-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unhandled exception #8
Comments
Can you verify that the "imageFile" is correct and the file has been generated and is in the given path? |
Can you please check if your TeX installation contains the program "dvipng.exe". This is required to convert the dvi to a png. |
I tested with sample2e from the latex base package. From the command line it only works it I type I temporarily fixed the issue by removing the path to the miktex installation and removing the extension. It now relies on existence of a working ps2pdf in my path. |
Thanks for reporting this problem. I will add some code to at least create a proper error message if ps2pdf is not found or returns an error. |
Hello Jan
I use Latex4CorelDRAW with the CorelDRAW Technical Suite 2018. It has worked on and off for years. Typically it worked again after logging off and on again, or restarting the computer. I have always built Latex4CorelDRAW from the source.
Recently it stopped working and only worked again after reinstallation of corelDRAW. Now, 1 month later it fails again, so I'm now reaching out to get some help debugging this.
I updated to the latest version of Latex4CorelDRAW, and as said use technical suite 2018. This worked one month ago, but no longer.
Perhaps this is the result of a library update in windows?
When I open a new document in CorelDRAW and add a Latex item, I get the edit window and can enter the latex code. I do get a preview.
When I click OK, I get the following error dialog:
The details are in the enclosed file "new 1.txt"
To me this is abracadabra.
When running a debug session, the code breaks at line 250 of LatexDialog.cs:
Can you provide any directions how to proceed debugging this problem?
Best regards,
Paul van der Hulst
new 1.txt
The text was updated successfully, but these errors were encountered: