Eli Iannuzzo
Topic Author
Posts: 5
Joined: 26 Mar 2020, 06:01

UIElement cutoff issue.

26 Mar 2020, 06:46

Hi,

We have been experiencing strange cutoff issues with our UI, when resizing UIElements by their ScaleTransform some or all of the UIElement cuts in & out.
Note: Running the xaml file in the Noesis: XamlPlayer yields the same cutoff issues as our implementation.
Note: Running the xaml file via internet explorer yields no such cutoff issues.

Attached below are two examples of the cutoff issue in action, honestly not sure why the cutoff effect is different for each.
How could we resolve the issue?
Attachments
IssueExample.7z
(1.26 KiB) Downloaded 11 times
 
User avatar
sfernandez
Site Admin
Posts: 1912
Joined: 22 Dec 2011, 19:20

Re: UIElement cutoff issue.

26 Mar 2020, 10:25

The cutoff problem was a known issue in 2.2.6 version related to opacity groups bigger than window size.
This was solved for 3.0 version used in our web xamltoy.

You can workaround this situation in case you can animate the opacity of a brush instead. In the attached CutoffExample.xaml you can write the animation like this:
<Storyboard x:Key="storyboard_anim" RepeatBehavior="Forever">
  <DoubleAnimationUsingKeyFrames Storyboard.TargetProperty="(Shape.Fill).(Brush.Opacity)" Storyboard.TargetName="Image1">
    <EasingDoubleKeyFrame KeyTime="0" Value="0"/>
    <EasingDoubleKeyFrame KeyTime="0:0:2" Value="1"/>
    <EasingDoubleKeyFrame KeyTime="0:0:4" Value="1"/>
    <EasingDoubleKeyFrame KeyTime="0:0:6" Value="0"/>
  </DoubleAnimationUsingKeyFrames>
  ...
</Storyboard>
Does that work in your case?
 
Eli Iannuzzo
Topic Author
Posts: 5
Joined: 26 Mar 2020, 06:01

Re: UIElement cutoff issue.

26 Mar 2020, 23:08

Thank you for the timely reply, unfortunately this solution does not cover all of our situations,
could you link the Issue ID for when this was solved so we're able to cherry pick the fix?
 
User avatar
sfernandez
Site Admin
Posts: 1912
Joined: 22 Dec 2011, 19:20

Re: UIElement cutoff issue.

30 Mar 2020, 16:31

You can find the fix in branch 2.2 revision 8712.

Who is online

Users browsing this forum: No registered users and 0 guests