Advanced programming

collapse

#
- 1.) Application.config
- 2.) Basic concepts
  - 1.) Composite pattern
    - 1.) Lifecycle
    - 2.) Programming
  - 2.) Properties
    - 1.) Local
    - 2.) Network
    - 3.) Persistance
    - 4.) Configuration
    - 5.) Logging
  - 3.) Synchronous Methods
    - 1.) Virtual methods
  - 4.) References
    - 1.) 1 Object
    - 2.) N Objects locally
    - 3.) N Objects Network
  - 5.) Events
  - 6.) Asynchronous methods
  - 7.) Configuration
    - 1.) Config storage
    - 2.) Overriding
  - 8.) Messages and Alarms
    - 1.) Alarms
  - 9.) Database
    - 1.) Usage
    - 2.) Extend
      - 1.) EF 4.0
      - 2.) EF 7.0
    - 3.) Persistable queries
  - 10.) Designs
    - 1.) GUI Design
      - 1.) Set and convert Properties
      - 2.) Styles and Setter
      - 3.) Property trigger
      - 4.) Datatrigger
      - 5.) Events & trigger
      - 6.) Animations
      - 7.) Resources
    - 2.) Reports
      - 1.) Programming
  - 11.) Diagnose and Debugging
  - 12.) Updates
- 3.) UI-Controls
  - 1.) UI-Library integration
  - 2.) iPlus-Controls
  - 3.) Custom Controls
- 4.) Application programming
  - 1.) Multithreading
  - 2.) Businessobjects
    - 1.) Navigationless
    - 2.) Navigable
    - 3.) Context dependant dialogs
    - 4.) Background Tasks
  - 3.) Manager classes
  - 4.) Process applications
  - 5.) Workflow classes
  - 6.) External systems
    - 1.) Mobile devices
    - 2.) OPC UA Communication
      - 1.) Server
    - 3.) Simatic S7
  - 7.) Bit masking
- 5.) []

;

Usage of Styles

In the previous chapter "Setting & converting properties" you learned how to set a dependency property directly or change it using converters if properties in the model (or one or more ACComponent instances) change.

However, the converter technology has the disadvantage that methods have to be provided which carry out a type conversion. This can be circumvented using other WPF techniques. One of them is the use of styles and triggers , which will be discussed in the following subsections.

But you have to decide which technique you want to use. Both cannot be used at the same time! In the case of the "rectangle example", this means that you must not set the "Fill" property directly, but indirectly by using the setter class within a style.

The first step is therefore always to define a style by opening the triangle at the top right and calling the "Edit Style Setter" command:

Set UI-Properties via Setter-class

The style window opens, in which you can then set the graphic properties. Select a property from the list in the left half of the window. Use the "Add" button to apply the property to the style. You can then set the value of the property in the list on the right.

For our rectangle example, take the Fill property and then change the fill color:

Close the style window and switch to the XAML editor. The following code was generated:

The Fill property is no longer set directly, but by means of the setter declaration. Styles and setters are the prerequisite for triggers. For this reason, you should first add any properties that you want to change dynamically with triggers in the "Style.Setters Collection".

Cookie settings