Ahh, so that's how it works. I didn't realize there was more to the
constructor then a normal event. That will teach me not to check the API
reference first.  ;-)

Thank you both for the info!

~Aaron

On Sun, Jun 29, 2008 at 7:02 PM, Daniel Gold <[EMAIL PROTECTED]> wrote:

>   It is used as the default Binding event and you can create one using the
> static method createUpdateEvent on the PropertyChangeEvent class
>
> var changeEvent:PropertyChangeEvent =
> PropertyChangeEvent.createUpdateEvent(changedObject,changedProperty,oldVal,newVal);
> dispatchEvent(changeEvent);
>
> That should fire the binding for the property you've updated.
>
>
> http://livedocs.adobe.com/flex/3/langref/index.html?mx/events/PropertyChangeEvent.html&mx/events/class-list.html
>
>
> On Sun, Jun 29, 2008 at 8:56 PM, Josh McDonald <[EMAIL PROTECTED]> wrote:
>
>>   Off the top of my head, when you instantiate a PropertyChangeEvent
>> instead of an Event, the constructor is expecting more useful information
>> about what field changed and when that information is missing / invalid the
>> requisite bindings don't fire. But when the binding handlers get a generic
>> event of name PropertyChangeEvent.PROPERTY_CHANGE, they just assume the
>> entire object has been updated and update all bindings to that object.
>>
>> All just a guess tho ;-)
>>
>> -Josh
>>
>>
>> On Mon, Jun 30, 2008 at 11:48 AM, Aaron Miller <
>> [EMAIL PROTECTED]> wrote:
>>
>>>  Hello,
>>>
>>> when I do this:
>>>
>>> dispatchEvent( new
>>> PropertyChangeEvent(PropertyChangeEvent.PROPERTY_CHANGE) );
>>>
>>> My bindings do not execute.
>>>
>>>
>>> When I do this:
>>>
>>> dispatchEvent( new Event('propertyChange') );
>>>
>>> They do (using default binding with no meta data specified).
>>>
>>>
>>> What is what is the PropertyChangeEvent.PROPERTY_CHANGE event used for if
>>> not for binding?
>>>
>>>
>>> Thanks for any input!
>>> ~Aaron
>>>
>>>
>>>
>>>
>>
>>
>> --
>> "Therefore, send not to know For whom the bell tolls. It tolls for thee."
>>
>> :: Josh 'G-Funk' McDonald
>> :: 0437 221 380 :: [EMAIL PROTECTED]
>>
>
>  
>

Reply via email to