locked
Where is FlowDirection property? - 1 attachment (Tor Langlo) - 1/3/2008 5:56 PM PST RRS feed

  • Question

  • By: Tor Langlo


    I want to swap the order of the check and the text in a CheckBox. The only
    way I know to do that (w/o replacing the template) is by setting
    'FlowDirection="RightToLeft"'. Unfortunately, the FlowDirection property is
    nowhere to be found in Blend's property editor.

    If I set the property manually in xaml, I get the expected result at
    runtime, but at designtime the checkbox seems to think the flow direction
    still is LeftToRight.

    Bug?

    Tor Langlo
    Friday, February 22, 2008 3:44 PM

All replies

  • Brennon Williams


    Howdy Tor,
    
    I am not sure if it is a defect or not, but as you say it would nice to have 
    both an exposed property and a design time represenation of the 
    FlowDirection. You will find that the same is true for all controls, that the 
    flow is applied at runtime.
    
    A lot of discussion is centered around visual context at the moment, and the 
    issues that designers are having with having a complete context to work 
    against. This issue underlines a problem that I raised within the same 
    context, that when building an application that needs to be localised, 
    context is just as important as some language translations are based on 
    context. FlowDirection being a primary importance to this aswell.
    
    Hopefully this post will generate some additional discussions surrounding 
    the issue.
    
    Cheers
    
    
    -- 
    Want to learn how to use Blend and visual studio?
    
    http://www.learnexpressionstudio.com
    http://www.expressionblend.com
    http://www.x-coders.com
    
    
    "Tor Langlo" wrote:
    
    > I want to swap the order of the check and the text in a CheckBox. The only 
    > way I know to do that (w/o replacing the template) is by setting 
    > 'FlowDirection="RightToLeft"'. Unfortunately, the FlowDirection property is 
    > nowhere to be found in Blend's property editor.
    > 
    > If I set the property manually in xaml, I get the expected result at 
    > runtime, but at designtime the checkbox seems to think the flow direction 
    > still is LeftToRight.
    > 
    > Bug?
    > 
    > Tor Langlo
    > 
    > 
    Friday, February 22, 2008 11:39 PM
  • Tor Langlo


    Hi Brennon,
    
    > A lot of discussion is centered around visual context at the moment,
    > and the issues that designers are having with having a complete
    > context to work against. This issue underlines a problem that I raised
    > within the same context, that when building an application that needs
    > to be localised, context is just as important as some language
    > translations are based on context. FlowDirection being a primary
    > importance to this aswell. 
    
    Can you explain what you mean by "visual context" here?
    
    Tor.
    
    Friday, February 22, 2008 11:39 PM
  • Brennon Williams


    Howdy Tor,
    
    Visual Context is taken as being able to see a "complete" picture, so for 
    instance, if you are building a usercontrol in Blend, you only get to see the 
    usercontrol on the screen and not the entire Window (or parent control) that 
    the current work space is involved in. It makes for poor productivity having 
    to build, then switch back to a control or Window just to see if everything 
    fits... make some changes and try again.
    
    Designers are typically painting an entire picture (as is done with 
    ilustrator etc) and then breaking the parts up as required after it is 
    complete, but with Blend, to build an application that conforms to good 
    object orientated design principals, you need to build the parts first and 
    then bring them alltogether to make the complete picture.
    
    This workflow is completely backwards to what is the "norm" for a designer.
    
    Compare Blend against something like Flash/Flex which does precisely this 
    (allows the designer to work on the control with the rest of the canvas 
    greyed out). This sort of priority for the importance of the Visual Context, 
    says that MS need to keep working to try and understand the designer and 
    their processes better.
    
    Now we all know that I love Blend, so no flaming me on this... this is just 
    an observation and an explanation of some of the frustatrations designers 
    have with blend. 
    
    I believe that the Blend team is fully stocked with people that will make 
    this sort of functionality a reality in future releases. Every new release of 
    Blend we see contains great improvements, but if it was my team I would 
    certainly put everything else on hold until this is implemented.
    
    
    Cheers for listening to me rattle on, but if there is any designer out there 
    that thinks I have it wrong (after all I am a developer) please let me know. 
    I am very interested at learning how to make your life easier with better 
    processes from the XAML architects point of view.
    
    
    
    -- 
    Want to learn how to use Blend and visual studio?
    
    http://www.learnexpressionstudio.com
    http://www.expressionblend.com
    http://www.x-coders.com
    
    
    "Tor Langlo" wrote:
    
    > Hi Brennon,
    > 
    > > A lot of discussion is centered around visual context at the moment,
    > > and the issues that designers are having with having a complete
    > > context to work against. This issue underlines a problem that I raised
    > > within the same context, that when building an application that needs
    > > to be localised, context is just as important as some language
    > > translations are based on context. FlowDirection being a primary
    > > importance to this aswell. 
    > 
    > Can you explain what you mean by "visual context" here?
    > 
    > Tor.
    > 
    Friday, February 22, 2008 11:40 PM
  • mg


    using VS2008 designer for XAML -lack features, visibility bugs, etc.
    using Blend - no FlowDir support, no HierarchicalDataTemplate support, etc.

    Microsoft, are you seriously supporting WPF or making a joke?!


    "Brennon Williams" wrote:

    > Howdy Tor,
    >
    > I am not sure if it is a defect or not, but as you say it would nice to have
    > both an exposed property and a design time represenation of the
    > FlowDirection. You will find that the same is true for all controls, that the
    > flow is applied at runtime.
    >
    > A lot of discussion is centered around visual context at the moment, and the
    > issues that designers are having with having a complete context to work
    > against. This issue underlines a problem that I raised within the same
    > context, that when building an application that needs to be localised,
    > context is just as important as some language translations are based on
    > context. FlowDirection being a primary importance to this aswell.
    >
    > Hopefully this post will generate some additional discussions surrounding
    > the issue.
    >
    > Cheers
    >
    >
    > --
    > Want to learn how to use Blend and visual studio?
    >
    >
    http://www.learnexpressionstudio.com
    > http://www.expressionblend.com
    > http://www.x-coders.com
    >
    >
    > "Tor Langlo" wrote:
    >
    > > I want to swap the order of the check and the text in a CheckBox. The only
    > > way I know to do that (w/o replacing the template) is by setting
    > > 'FlowDirection="RightToLeft"'. Unfortunately, the FlowDirection property is
    > > nowhere to be found in Blend's property editor.
    > >
    > > If I set the property manually in xaml, I get the expected result at
    > > runtime, but at designtime the checkbox seems to think the flow direction
    > > still is LeftToRight.
    > >
    > > Bug?
    > >
    > > Tor Langlo
    > >
    > >
    Friday, February 22, 2008 11:40 PM