This will be terrible UX as scrolling will mix with panning. Preferred size is generally problematic for peer components, you should never rely on it. I suggest using something like table layout to explicitly determine the size of the component based on screen size percentages.
The native OS has preferred size methods but for things like maps they don't mean much. Furthermore, they run on the native thread so by the time we get them back we no longer need them. There isn't much we can do about it. -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/1bc957f0-5722-4734-afdd-093ffc104e30%40googlegroups.com.
