Anyway, I think I found an odd behavior with the configuration in the test case. Forget about center behavior, it can be changed and the issue persists. To reproduce it, just scroll Y containers freely and before it stops scrolling, swipe to another tab. Now try to scroll the current containers, and you'll see that they are blocked.
Not a big problem to me because I make use of setSnapToGrid(true) which prevents this from happening. But I just wanted to let you know... On Friday, June 24, 2016 at 9:55:53 AM UTC+2, Carlos Verdier wrote: > > Yes, you're right, sorry. > > I found the problem. Apparently, I wrote t.setEagerSwipeMode(true) to test > the behavior and totally forgot about it! It is working as expected now. > > Yesterday I was too tired, it was late and I was unable to see a trivial > error like that. My mistake :) > > Thanks > > On Friday, June 24, 2016 at 6:50:43 AM UTC+2, Shai Almog wrote: >> >> Hi, >> we try to stick to updating only on Fridays and this week we were >> successful. No updates were made for the servers until later today. >> >> If the problem happens in 3.4 it's because of a change you made to the >> code as that is static. >> >> Looking at the code you should not use that center behavior for a UI of >> the type you chose. It shouldn't have worked to begin with. >> When we say border layout CENTER we always mean the default behavior >> which is scale unless explicitly stated otherwise... >> > -- 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 codenameone-discussions+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/codenameone-discussions. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/63b18245-f2a3-4ed5-a77b-c9b1ec98129a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
