Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You said:</p> <blockquote> <p>On creation complete my parent component executes an "init" function which simply sets public bindable variables in child components. I'd like the child components to watch these variables and upon being set use them.</p> </blockquote> <p>It breaks encapsulation to try to have the child component access the parent. Parents can access, children, but children should never access parents. However, any given component should be aware of when it's values changes and update itself accordingly. The use of get/set properties and the Flex Component LifeCycle are the proper way to do that. </p> <p>When you make a component Bindable that means it can be used as the source of data binding. It almost sounds to me like you're trying to use said properties as the target for data binding and are struggling to update your component. </p> <p>If I understand what you're after, I wouldn't use the ChangeWatcher at all. Just expand your user property into a get/set property and either implement your changes in the set method of the property, or possibly in commitProperties using a flag. </p> <p>Something like this:</p> <pre><code>private var _user : Object; [Bindable] public function get user():Object{ return this._user; } public function set user(value:Object):void{ this._user = value; Alert.show(value); } </code></pre> <p>Or even better:</p> <pre><code>protected var userChanged : Boolean = false; private var _user : Object; [Bindable] public function get user():Object{ return this._user; } public function set user(value:Object):void{ this._user = value; this.inalidateProperties() userChanged = true; } public function commitProperties():void{ if(userChanged == true){ Alert.show(value); userChanged = false; } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POChangeWatcher not firing on bound property change
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJeffryHouser
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POChangeWatcher not firing on bound property change
      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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO@Flextras: Thanks for the explanation. Your suggestions achieve EXACTLY what I was after. However, why is the 2nd approach better then the 1st?
      singulars
      1. PO
      1. UStommac
    2. CO@tommac The 2nd approach is better because it allows you to coordinate different property changes at the same time, and consolidate code for implementing changes. The need is not obvious in This simple example. But, if I take take a more complex component, such as the Flextras Calendar I can better demonstrate. Three properties control which month is displayed: displayedMonth, displayedDate, and displayedYear. All execute similar code when changed. By using the component lifeCycle, if someone changes all 3 in succession, the component only updates itself once not three times. Make sense?
      singulars
      1. PO
      1. USJeffryHouser
    3. CO@Flextras: From your example, I conceptually understand the difference and benefit of using the 2nd approach. With that said, I'm curious to see it implemented. Do you know where I can find an example implementation?
      singulars
      1. PO
      1. UStommac
 

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