TableViews use ScrollViews.
Can you file a bug report on this please. You must include a build.settings and config.lua in the zip file.
Thanks
Rob
HI Rob
I am updating a business App and I having exactly the same issues. I am using 2288 so a much newer build in CompatibilityMode = 1
If I move to compatibiltyMode = 2 will this fix this problem
note the work around doesn’t really fix the issue, sometimes the content appears in the correct position but then scrolls down so there’s 2/3 a screem of blank
I’ve tried playing around with the pad values but no luck either
@dominic.wood8, there isn’t a compatibliyy mode = 2. You either have a:
graphicsCompatibility = 1
line in your config.lua or you don’t. I suppose setting it to anything other than 1 would work, but the official thing is to not have the line for Graphic 2.0 builds.
I can’t find a bug report for this. If you can build a small sample that shows the problem (you must also include your build.settings and config.lua files in a .zip file) and file a bug report using the “Report a Bug” feature a the top of the page.
Thanks
Rob
thanks for the reply, don’t worry I’ve not used =2 but I wanted to know that if I went to the effort changing the app to graphics 2.0 the issues would stop.
As I can’t build with pre v2.0 any more I’m trying to track down what is happening, I have nothing to compare it with.
Do you know if the coords of the :scrollToPosition are calculated with the new coords system when compiling with the latest builds? If they are I think what is happening is that the scrollview starting coordinate is wrong causing the scroll view to ‘bounce’ and appear too far down.
Ditto does :scrollTo(“top”, {time = 250}) work?
Again I can’t compare ‘old’ and ‘new’ scrollviews but it now has a huge amount of ‘bounce’ so when you scroll past the top it pings back with the content you want to see in the wrong place. So now its hard to scroll to the top of your content
I haven’t put in a bug as I would have any issues would have been fixed by now especially as I had read the the pad was working in one of the latest daily builds.
Great if you could answer regarding the coords system of the :scrollTo(
Just done some more testing I can confirm the problem. When using the line a
scroller:scrollTo(“top”,{time = 250})
the scrollView appear to start at the top or maybe just a line or two above, this causes a crazy bounce to scroll your content so it starts 2/3 the way down the screen.
can you confirm the :scrollTo works on your code examples, as I have read that scrollview behaviour is now eratic… will converting to graphics 2 fix this?
I don’t think this is only related to ScrollView, I have exactly the same issue with tableview, anyone else?
TableViews use ScrollViews.
Can you file a bug report on this please. You must include a build.settings and config.lua in the zip file.
Thanks
Rob