Hi,
> I'm curious, why does Adobe recommend not to use a datagrid on mobile? Is
> it too heavy of a component, or is there a more technical reason?
A bit of both, moe that it wasn’t optimised for small mobile screen and touch
interaction.
> Was it only a concern on early mobile devices, but no
this message in context:
http://apache-flex-users.246.n4.nabble.com/Datagrid-on-a-Mobile-Device-tp13702p13709.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
Hi,
> Also a very good idea that I will look into further. I am using the Spark
> Data grid
You can get at and change the horizontal and vertical scroll positions.
grid.layout.verticalScrollPosition / grid.layout.horizontalScrollPosition off
top of my head. The grid.ensureCellIsVisible() may a
Also a very good idea that I will look into further. I am using the Spark
Datagrid
--
View this message in context:
http://apache-flex-users.246.n4.nabble.com/Datagrid-on-a-Mobile-Device-tp13702p13707.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
lex-users.2333346.n4.nabble.com/Datagrid-on-a-Mobile-Device-tp13702p13706.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
more. Any
other suggestions, or does everyone agree that this is this best approach?
--
View this message in context:
http://apache-flex-users.246.n4.nabble.com/Datagrid-on-a-Mobile-Device-tp13702p13705.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
several datagrids and change their visibility using the "previous"
> and "next" button?
>
>
>
> --
> View this message in context: http://apache-flex-users.
> 246.n4.nabble.com/Datagrid-on-a-Mobile-Device-tp13702.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com.
>
ility using the "previous"
and "next" button?
--
View this message in context:
http://apache-flex-users.2333346.n4.nabble.com/Datagrid-on-a-Mobile-Device-tp13702.html
Sent from the Apache Flex Users mailing list archive at Nabble.com.
