Skip to main content
12-Amethyst
March 4, 2015
Question

Multi-line equation parentheses and integral symbols display as broken / dashed lines

  • March 4, 2015
  • 6 replies
  • 2107 views

The PTC Mathcad team has been working with Microsoft on this specific issue, which was created when Microsoft fixed a bug in .NET 4.5 which then had an undesirable side-effect on how Prime is able to render multi-part text symbols. The most visible impact is that adjacent lines can become misplaced and/or disconnected.

Microsoft has been working on a solution for us, but they will not undo their original bug fix. The fix they provide PTC will allow choosing between the old and new behavior by application.

Due to Microsoft's Dual Branching Servicing Model the fix will need to be deployed in a Limited Distribution Release, which means that Microsoft is addressing Prime’s specific issue in a *hotfix* that PTC will make available to our customers. The PTC Mathcad team will test the hotfix once received from Microsoft, and as soon as we validate that there are no regressions we will begin making it available to customers.

It is important to note that this issue is purely a visual issue and in no way impacts the calculations in Prime.

6 replies

1-Visitor
March 5, 2015

Display Postscript would have been a solution to this problem - WYSIWYG and WYSIWY Print. It was the basis for NeXT OS display; Display PostScript - Wikipedia, the free encyclopedia

It's all lost opportunity; too bad that solutions to today's problems were solved almost 30 years ago. At least OpenGL, of similar age, manages to stay along with the pack.

Any clue about what problem MS was working to fix? There must have been a benefit somewhere.

bedmonds12-AmethystAuthor
12-Amethyst
June 29, 2015

Microsoft has bundled our hotfix and it is now available for customers to download here.

1-Visitor
June 30, 2015

Hi Brent,

I have a question. Will this "hot fix" be included in future releases of Mathcad Prime?

Thanks.

bedmonds12-AmethystAuthor
12-Amethyst
July 1, 2015

The hotfix will be included in future versions of Microsoft's .NET platform (it is already rolled up into the pre-release .NET 4.6).

JeffH1
16-Pearl
November 10, 2015

.NET 4.6 does not seem to have fixed the problem and the hotfix will only apply to .NET 4.5.2.  Are we sure that this "hotfix" was rolled into the .NET 4.6 release?

24-Ruby IV
June 4, 2016

Here is the correct link for this Microsoft hotfix: https://support.microsoft.com/en-us/kb/3009698