Skip to content
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

\thinspace exception #139

Closed
AndrewXS opened this issue Jul 6, 2018 · 6 comments · Fixed by #214
Closed

\thinspace exception #139

AndrewXS opened this issue Jul 6, 2018 · 6 comments · Fixed by #214
Assignees
Labels

Comments

@AndrewXS
Copy link

AndrewXS commented Jul 6, 2018

Start the WpfMath.Example project.
Clear the starting formula in the textbox.
Enter "\,"
An exception is thrown in TexPredefinedFormulaParser.cs

@AndrewXS AndrewXS changed the title \\thinspace exception \thinspace exception Jul 6, 2018
@B3zaleel
Copy link
Contributor

B3zaleel commented Jul 7, 2018

Are you sure this is an issue. I did exactly what you did and no Exceptions were thrown.

@AndrewXS
Copy link
Author

I'm running the WpfMath 0.5 code from 2018-05-08. Debug build in VS Enterprise 2017 Version 15.5.6. Just tried again, same problem. You entered the backslash and the comma?

@B3zaleel
Copy link
Contributor

Yes I did

@B3zaleel
Copy link
Contributor

Maybe you typed a period

@AndrewXS
Copy link
Author

AndrewXS commented Jul 12, 2018

No, not a period. However, I just tried all of the spacing commands ( \, \; \: \! ), and they cause the exception.

The attached image shows the exception with \;. (The source is {\;})

wpfmath_exception

@ForNeVeR ForNeVeR self-assigned this Jul 12, 2018
B3zaleel added a commit to B3zaleel/xaml-math that referenced this issue Oct 11, 2018
Fixed the exception thrown when inserting the short forms of some space atoms.
@B3zaleel
Copy link
Contributor

@AndrewXS Please check the branch connected to #166 to see if it solves this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants