Charts can't be printed

Wanted to print a chart, printer does not start, restart Charts i’m getting the:
A JavaScript error occurred in the main process
Uncaught Exception:
Type Error: Object has been destroyed
Reinstall Charts did not not work.

Chart Version is 8.16

Hello Eduard! Welcome to the forum.

Thanks for the report, we’ll investigate this issue ASAP!

Kind Regards,
Malte

Hello again Eduard!

I’d like to ask for some more details regarding this case.

Do you mean that you can’t open the Charts app even after reinstalling it?

Does this happen every time you try to print a chart? Can it happen for any chart? The reason for the questions is that we have not seen this ourselves despite printing multiple charts, so it is a bit hard for us to diagnose the issue.

Apologies for the inconvenience!

Kind Regards,
Malte

Hello Malte

Thank you for your kind effort.

These are the steps to create the problem:

For exemple:
-I start the PC
-Then I start the Charts app
-I search for an airport, for exemple LOWI
-Approach LOC 26
-It opens the chart, i want to print it
-in the above menu on the right is located a icon to print it
-i click on it, nothing happens, printer does not start
-i close Charts
-then i want to search for another airport, so i reopen Charts again
-does not start, i comes the following message:

A JavaScript error occurred in the main process
Uncaught Exception:
Type Error: Object has been destroyed

-reinstall Charts, still same issue

Charts works, but no print any chart. If I don’t want to print, Chart seems to work fine.

WIN 11 Pro, Build 22621, Printer Brother DCP 9020

Kind regards

Eduard

Thanks for the very detailed description!

The issue has been identified and will be fixed in the next update. Thanks again for the feedback!

Kind Regards,
Malte

Don’t worry, happy to help you

Freundliche Grüsse

Ed. Truog

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.

Hi,

Please update to the latest version which was released today. The issue has been fixed.

Kind regards,

Stephen