I don't think there's a significant danger of that. As the feature request would really only be useful at a group level for this (or perhaps at a stack level if only considering standard v retina ios) and we would still need to know the scale to apply I think it could be a drop in replacement for any scaling routine we invent.
So... How do we handle this in the most flexible and least intrusive way? One idea that comes to mind is to allow the developer to choose between the framework handling the density change, the framework dispatching a message to the control and doing nothing. Cheers -- M E R Goulding Software development services mergExt - There's an external for that! On 28/07/2012, at 12:13 AM, Richard Gaskin <ambassa...@fourthworld.com> wrote: > So my point was merely the hope that any effort to address this without > engine support would not be misconstrued as there being no need for engine > support _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
