scrolling wil not mix with panning as the drag event is consumed by the map 
when occuring on the map so scrolling would only occur when the drag event 
is outside the map. This king of UI is used in many apps.
Anyway bad UX or not, this doen't answer the question of how to have a 
native component that is part of a scrollable container (it can be a native 
map that is purely static (all controls disabled) or just clickable but not 
pannable or event just any browserwebview displaying some html content). 
And setting the parent component scrollable or using a layout different 
from LayeredLayout for the parent shouldn't affect the way the 
peercomponent is displayed (see the ticket oppened on github for details).
As for the preffered size, I don't apply it to the peercomponet directly 
but to a wrapping CN1 Container. So I might as well have used a table 
layout with a screen size percentage, the issue would have been the same 
(the dimensions of this wrapping component is OK in any cases, this is only 
the peercomponent it contains that has wrong dimensions and sometimes 
exceed it and is cropped to its boundaries)



On Thursday, August 29, 2019 at 4:41:47 AM UTC+2, Shai Almog wrote:
>
> 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/f1af0d55-2e7f-4e0f-be75-e80028bf6538%40googlegroups.com.

Reply via email to