Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Sorry, I couldn't reproduce your problem.</p> <p>I started Visual C# 2010 Express, created a new 'WPF Application', added your XAML to a <code>UserControl</code> that I imaginatively titled <code>UserControl1</code>, and added your <code>ItemsControlBehavior</code> class. I then modified the MainWindow that VC# created for me as follows:</p> <p>MainWindow.xaml (contents of <code>&lt;Window&gt;</code> element only):</p> <pre><code>&lt;StackPanel Orientation="Vertical"&gt; &lt;Button Content="Add user control" Click="ButtonAddUserControl_Click" /&gt; &lt;Button Content="Add message" Click="ButtonAddMessage_Click" /&gt; &lt;StackPanel Orientation="Horizontal" x:Name="sp" Height="300" /&gt; &lt;/StackPanel&gt; </code></pre> <p>MainWindow.xaml.cs:</p> <pre><code>public partial class MainWindow : Window { public ObservableCollection&lt;string&gt; Messages { get; private set; } public MainWindow() { InitializeComponent(); Messages = new ObservableCollection&lt;string&gt;() { "1", "2", "3", "4" }; DataContext = this; } private void ButtonAddUserControl_Click(object sender, RoutedEventArgs e) { sp.Children.Add(new UserControl1()); } private void ButtonAddMessage_Click(object sender, RoutedEventArgs e) { Messages.Add((Messages.Count + 1).ToString()); } } </code></pre> <p>I made no modifications to the XAML in your UserControl, nor to your <code>ItemsControlBehavior</code> class.</p> <p>I found that no matter how many user controls were added, their ScrollViewers all scrolled down to the bottom when I clicked the 'Add message' button.</p> <p>If you're only seeing the scroll-to-the-bottom behaviour on one of your user controls, then there must be something that you're not telling us.</p>
    singulars
    1. This table or related slice is empty.
    1. PODependency Property in User Control works only on the first instance
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USLuke Woodward
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COThank you for your attempts ! I'm gonna do the same with a very simple test project like you and see, if things work on it, what's different in my project and I'll keep this post updated. tks
      singulars
      1. PO
      1. USKitAndKat
    2. COOk it works simply like that. I don't know if it has something to do with it but in my real project I don't set programmatically View.DataContext = ViewModel, but I put it in a resources dictionnary like that : <DataTemplate DataType="{x:Type vm:UserControlViewModel}"> <View:UserControl1 /> </DataTemplate> maybe it creates only one view for several viewmodel ? separating instances when forced only ?
      singulars
      1. PO
      1. USKitAndKat
    3. CO@Anna Yes, if you create it in xaml, it will be create once and reused. There is a flag you can use to NOT share it using x:Shared="false" on your resource.
      singulars
      1. PO
      1. USdowhilefor
 

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