Databases
StackOverflow2013
Postsdbo
POBinding via XAML or Code behind
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBinding via XAML or Code behind
    primarykey
    data
    text
    <p>I'm creating a WPF application and at the top of the page I need to display a postal address. Underneath the postal address will be product information. The product information is returned from a datasource and bound to the datacontext. eg this.DataContext = myComplexType;</p> <p>Staff need to manually switch which postal address is to be displayed. I think the best way would be to select would be via a radio button control. In other words, on my Page, I would have 3 radio buttons, *UK Address *USA Address *China Address and depending on which was selected, the appropriate text would be entered in the Textblock Name="txbPostalAddress" at the top of the page.</p> <p>The postal addresses live within a class called Addresses (as strings). e.g. Code:</p> <pre class="lang-cpp prettyprint-override"><code>namespace DAL { public class Addresses { public string GctHkAddress { get { return gctHkAddress;} } public string GctUsaAddress { get { return gctUsaAddress; } } public string GctUkAddress { get{return gctUkAddress;} } private string gctHkAddress = "Company Name\n Hong Kong \n"; private string gctUsaAddress = "Company Name\n USA \n"; private string gctUkAddress = "Company Name\n UK \n"; } } </code></pre> <p>My question is, should the binding be done in XAML or in code behind. I can do it in code behind quite easily but I get the feeling this negates the power of XAML. Does any one have any idea which is the better approach and if via XAML, any idea how or links to tutorials etc?</p> <p>Thanks</p> <p>Dave</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USvyegorov
    1. USDave
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBinding via XAML or Code behind
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    2. VO
      singulars
      1. POBinding via XAML or Code behind
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload