Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>i would say a very simple and efficient way to solve this issue would be to use the INotifyPropertyChanged interface in order to use the Observer-Pattern.</p> <p>Let the container that fires the initial event be the observable part and let the two others observe it. So whenever the observable container does something (e.g. fires a click-event) the others will get informed and can react accordingly.</p> <p>Once your OutsideContainer class is observable, do these two steps:</p> <ol> <li><p>In the OutsideButton class fire the PropertyChanged event in appropirate place (e.g. where the "super"-click happens.</p></li> <li><p>In the ImageFade and ButtonFace class chatch the PropertyChanged event and do something (e.g. let them fire their own click-event).</p></li> </ol> <p>Try the following:</p> <p>In the code-behind file OutsideBoard.cs implement the INotifyPropertyChanged interface in order to make it observable:</p> <pre><code>class OutsideBoard : INotifyPropertyChanged { public event PropertyChangedEventHandler PropertyChanged; private void FirePropertyChanged (string property) { if (PropertyChanged != null) { PropertyChanged(this, new PropertyChangedEventArgs(property)); } } // the click- EventHandler of your UserControl public event Click_EventHandler (object sender, RoutedEventArgs e) { // your clicking code of your UserControl FirePropertyChanged("SuperClick"); } // rest of the code inhere ... } </code></pre> <p>Now every class that wants to observe the OutsideBorder class has to implement an EventHandler on that class:</p> <p>Write something like the following in your ButtonFade and ImageFade class:</p> <pre><code>outsideBorder.PropertyChanged += PropertyEventChangeHandler(MyClickHandling); public void MyClickHandling (object sender, PropertyChangeEventArgs e) { // do something } </code></pre> <p>So whenever the OutsideBoard class fires the PropertyChanged event, all observers will get notified by calling their MyClickHandling - method.</p> <p>Hope that will help you.</p>
    singulars
    1. This table or related slice is empty.
    1. POSilverlight: Can an event from one usercontrol begin an animation on a different usercontrol and/or the containing control
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTim Cooper
    1. USmarc wellman
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSilverlight: Can an event from one usercontrol begin an animation on a different usercontrol and/or the containing control
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMarc, thanks. Using INotifyPropertyChanged is how to do it but not precisely how you have shown above. What I did was have the child control (i.e. the one that actually contains the button and subsequently receives its event) implement the INotifyPropertyChanged interface. When one does that then all the containing user control has to do is subscribe to the PropertyChanged event and if another child control also needs to be notified then that other child can implement and expose a handler for PropertyChanged and the containing UserControl can subscribe the other child to the event.
      singulars
      1. PO
      1. USBob Rhinehart
 

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