Codejock Developer Community : BETA 3 XAML Parser Issues http://forum.codejock.com/ Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved. Thu, 21 May 2026 04:12:00 +0000 Thu, 05 Nov 2015 14:49:31 +0000 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 12.04 360 forum.codejock.com/RSS_post_feed.asp?TID=22744 <![CDATA[Codejock Developer Community]]> http://forum.codejock.com/forum_images/codejock-logo.gif http://forum.codejock.com/ <![CDATA[BETA 3 XAML Parser Issues : Your post has been submitted...]]> http://forum.codejock.com/forum_posts.asp?TID=22744&PID=74089&title=beta-3-xaml-parser-issues#74089 Author: Alopez
Subject: 22744
Posted: 05 November 2015 at 2:49pm

Your post has been submitted and corrections will be made. thank you for your patience and we will attempt to fix these errors soon. ]]> Thu, 05 Nov 2015 14:49:31 +0000 http://forum.codejock.com/forum_posts.asp?TID=22744&PID=74089&title=beta-3-xaml-parser-issues#74089 <![CDATA[BETA 3 XAML Parser Issues : A quick follow-up to my post above....]]> http://forum.codejock.com/forum_posts.asp?TID=22744&PID=73978&title=beta-3-xaml-parser-issues#73978 Author: markr
Subject: 22744
Posted: 02 October 2015 at 11:21am

A quick follow-up to my post above. It's not the ScrollViewer that appears to trigger this problem; it's the use of FontFamily. I can also reproduce the problem with the following simplified example:

<TextBlock FontFamily="Tahoma">
The Drive Space Panel provides you with an at-a-glance view of the used and free
        space on <Bold>each drive in your computer</Bold>.
</TextBlock>

Again, if the FontFamily tag is removed then the problem is reversed (extra whitespace is added, rather than existing white space being stripped).

Regards,

Mark R.
]]> Fri, 02 Oct 2015 11:21:51 +0000 http://forum.codejock.com/forum_posts.asp?TID=22744&PID=73978&title=beta-3-xaml-parser-issues#73978 <![CDATA[BETA 3 XAML Parser Issues : The XTP 17 BETA 3 XAML parser...]]> http://forum.codejock.com/forum_posts.asp?TID=22744&PID=73977&title=beta-3-xaml-parser-issues#73977 Author: markr
Subject: 22744
Posted: 02 October 2015 at 11:18am

The XTP 17 BETA 3 XAML parser has some problems.

First, there's something wrong with how the parser handles white space. Here's just one example. If you enter the following into MarkupPad you'll see that whitespace is not handled correctly:

<ScrollViewer TextBlock.FontFamily="Tahoma">
<TextBlock TextWrapping="Wrap" Margin="0,10,0,0">
       The Drive Space Panel provides you with an at-a-glance view of the used and free
        space on <Bold>each drive in your computer</Bold>.
      </TextBlock>
</ScrollViewer>

And here's how it actually gets rendered, which is incorrect:



Note that the above incorrectly handling of whitespace is only present if the scrollviewer is used. If you remove the ScrollViewer, the parser will actually add extra white space rather than remove it.

Also, RadioButton controls are not rendering correctly when Office 2010 themes are used. They are strangely pixelated, rather than smooth as they were in v16. Here's a screenshot of what I mean:



It's very important that markup render correctly, and I hope these types of issues will be addressed soon.

Regards,

Mark R.
]]> Fri, 02 Oct 2015 11:18:42 +0000 http://forum.codejock.com/forum_posts.asp?TID=22744&PID=73977&title=beta-3-xaml-parser-issues#73977