The Spark locked rows and columns code is new-ish so I’m not surprised
there are bugs.  Please file bugs with simple test cases, and/or offer
patches if possible.

MX DG was pretty aggressive about refreshing rows.  Spark DG may be
relying on change events more (or could just have bugs) so make sure you
aren’t seeing binding warnings at compile time or in the trace output at
runtime.

-Alex

On 1/8/15, 6:44 PM, "DavidM" <dmos...@gmail.com> wrote:

>Replaced Spark Datagrid with Mx Datagrid, left everything else the same,
>and
>data binding problems disappeared.
>
>So, I'm convinced that Spark Datagrid has issues with databinding.
>
>These definitely seem broken:
>
>1) Cells in locked columns don't always update, both in the case when a
>whole dataitem is replaced and readded and also when just the bindable
>property for that dataitem's cell is updated.
>
>2) Locked rows don't always reappear when all the data items are removed
>from a collection and then added back.
>
>As noted above, when changing just the Datagrid from Spark to Mx, with
>exactly the same Arraycollection and using the same class for the items in
>the array, and without changing any of the code, then neither of these
>problems are seen in the Mx Datagrid!
>
>Note: when changing any property and when adding/removing items from the
>array, I'm calling array.refresh()
>
>
>
>
>--
>View this message in context:
>http://apache-flex-users.2333346.n4.nabble.com/Databinding-with-SparkGrid-
>and-locked-headers-columns-seems-broken-tp9362p9363.html
>Sent from the Apache Flex Users mailing list archive at Nabble.com.

Reply via email to