did you use [Bindable] in your dataprovider class defination? if now please
use it. otherwise ObjectProxy class.

On Fri, Jan 9, 2015 at 7:35 AM, DavidM [via Apache Flex Users] <
[email protected]> wrote:

> Seeing very strange behavior with Spark Datagrid when adding / removing
> items.
>
> As best I can tell, the cells in a locked column don't reliably update
> either when items are added/removed from an ArrayCollection and when the
> data for a bindable cell in a locked column is changed.
>
> I've been trying to use BindingManager to watch for caught exceptions but
> I'm not getting it to work, which is a pity as that would be helpful.
>
> I've tried:
>
> BindingManager.debugBinding('grid1.dataProvider')
>
> where 'grid1' is the id of the Spark Datagrid.
>
> any suggestions?
>
> I'm going back to MX Datagrid to see if the same problem can be replicated
> there.
>
> David
>
>
> ------------------------------
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://apache-flex-users.2333346.n4.nabble.com/Databinding-with-SparkGrid-and-locked-headers-columns-seems-broken-tp9362.html
>  To unsubscribe from Apache Flex Users, click here
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=cHJhc2hha3VtYXJAZ21haWwuY29tfDF8LTU0MTcyMzE2NA==>
> .
> NAML
> <http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>



-- 
*Regards,*
Prashant Kumar* | *Mob.: +91 8408811225




--
View this message in context: 
http://apache-flex-users.2333346.n4.nabble.com/Databinding-with-SparkGrid-and-locked-headers-columns-seems-broken-tp9362p9364.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.

Reply via email to