This binding is more complex than the others because it passes a value to a
formatter method, so it seems to me that it's more likely to throw an error.
text="{moneyFormatter.format(data.price)}"
- Josh
On Wed, Nov 16, 2016 at 11:19 PM, bilbosax <waspenc...@comcast.net> wrote:
> I can tell from using Scout that a large chunk of time is used doing
> measuring, which I assumed was because of the calculation of sizing
> everything. I chose to use groups because I found out very quickly that on
> mobile, pixel densities and screen resolutions vary a lot among the large
> number of devices. This causes problems because if you use an absolute
> number for X or y, it may get scaled based on the pixel density of your
> device leading to unexpected results. Going with percentage-based Groups
> insured that everything would look right regardless of the device. I guess
> the cost is performance. Tomorrow, I will try to lay everything out using
> absolute positioning. I just don't know if it will turn out significantly
> faster because I will still have to manually calculate the distance of all
> of these elements.
>
> So I can work on the performance issues of the renderer, but what about
> these hundreds of TypeErrors? Do you see anything in my code that could be
> triggering those?
>
>
>
> --
> View this message in context: http://apache-flex-users.
> 2333346.n4.nabble.com/Scout-What-does-this-mean-tp14126p14140.html
> Sent from the Apache Flex Users mailing list archive at Nabble.com.
>
