Using a setter to add a rendertransform

I'm wondering the same thing. Still, it's the only thing I can think of so far. I thought of the MultiDataTriggers option, but I don't just have two boolean properties. I actually have three properties, one of which can have three different possible values, another which has 5 different possible values and another which has seven different possible values. Creating triggers for all possible combinations would be a disaster.

I'm not keen about adding an offset property to whatever I'm binding to. That'd couple that class way to strongly to WPF... if I decide to use another framework, I'd have to rewrite the entire thing. Besides, that exposes information about how I want to present the object in this particular case... not a very versatile solution.

The thing is... adding multiple rendertransforms is easy enough:

< 

 

 

 

      <ScaleTransform ScaleX="4.5" ScaleY="4.5" /> </Path.LayoutTransform>

   

 

 


   

   <Path.RenderTransform>

      <TransformGroup>

<TranslateTransform x:Name="PropertyATranslation" Y="0" /> <TranslateTransform x:Name="PropertyBTranslation" Y="0" /> </TransformGroup> </Path.RenderTransform> </Path>

 I just can't figure out how to make a setter add something to a property's value rather than replacing it. I also tried naming the transforms and setting a different one for each case:

<Path Name="Thing" Fill="Black"> <Path.LayoutTransform> 

 

 

      <ScaleTransform ScaleX="4.5" ScaleY="4.5" /> </Path.LayoutTransform>

   

 


   

   <Path.RenderTransform>

      <TransformGroup>


   

 



<TranslateTransform Y="50" /> <TranslateTransform Y="30" /> </TransformGroup> </Path.RenderTransform> </Path>


 

And then have the trigger for property A set PropertyATranslation's Y property and have the trigger for property B set PropertyBTranslation's Y property, but for some reason it can't find them by name.

Edit: Oh, Channel 9. I hate your forum software so much.

That's not a bad idea. If all else fails, I'll give it a shot. I'll refrain from giving any examples of what I'm trying to do, because the Channel 9 editor just keeps screwing up my XAML.

One more try with this editor...

I figured this would solve my problem:

 <DataTemplate x:Key="ThingTemplate" DataType="Thing">
        
        <Path Name="Thing" Fill="Black">
            <Path.LayoutTransform>
                <ScaleTransform ScaleX="4.5" ScaleY="4.5" />
            </Path.LayoutTransform>
            <Path.RenderTransform>                
                <TransformGroup>
                    <TranslateTransform x:Name="FooTranslation" Y="0" />
                    <TranslateTransform x:Name="BarTranslation" Y="0" />
                </TransformGroup>
            </Path.RenderTransform>
        </Path>        
        
        <DataTemplate.Triggers>
            <DataTrigger Binding="{Binding Path=Foo}" Value="True">
                <Setter TargetName="FooTranslation" Property="Y" Value="50" />
            </DataTrigger>
        </DataTemplate.Triggers>

        <DataTemplate.Triggers>
            <DataTrigger Binding="{Binding Path=Bar}" Value="True">
                <Setter TargetName="BarTranslation" Property="Y" Value="30" />
            </DataTrigger>
        </DataTemplate.Triggers>
</DataTemplate>

I figured that this would achieve what I'm doing, but the compiler tells me that it can't find the Trigger target FooTranslation or BarTranslation.

You've got a point there, that's probably it. Ugh.

Thanks, that sounds like the right approach. I'm going to look into that. Just so I'm clear: how would I bind the above DataTriggers to the object itself rather than one of its properties? Just {Binding}?