Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Why not have a central object that will keep track of how many times the onEvent method was fired for all the listener classes</p> <pre><code> public interface CountObserver { public void updateCount(String className); public int getCount(String className); } public class CentralObserver implements CountObserver { private int aCount; private int bCount; public void updateCount(String className) { //There's probably a better way to do this than using //all these if-elses, but you'll get the idea. if (className.equals("AclassName")) { aCount++; } else if (className.equals("BclassName")) { bCount++; } } public int getCount(String className) { if (className.equals("AclassName")) { return aCount; } else if (className.equals("BclassName")) { return bCount; } } class A implements Listener { CountObserver countObserver; public void registerObserver (CountObserver countObserver) { this.countObserver = countObserver; } public void onEvent(char e) { if(e == 'a') { countObserver.updateCount (this.getClass.getName); } } } //Same thing for B or any other class implementing Listener. Your Listener interface should, of //course, have a method signature for the registerObserver method which all the listener classes //will implement. class Run { private A a; private B b; private CountObserver centralObserver; public runProgram () { centralObserver = new CentralObserver(); a.registerObserver(centralObserver); b.registerObserver(centralObserver); //run OnEvent method for A a couple of times, then for B } public int getAcount () { return centralObserver.getCount(a.getClass.getName()); } public int getBcount () { return centralObserver.getCount(b.getClass.getName()); } } //To get the sum of all the counts just call getAcount + getBcount. Of course, you can always add more listeners and more getXCount methods </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POProper coupling for multiple listeners that need to accessed shared state data
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USSandman
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POProper coupling for multiple listeners that need to accessed shared state data
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COThanks. This is a good idea, but it is a little different that what I am looking for. I will refactor the example to show it better.
      singulars
      1. PO
      1. USJosh
 

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