Re: iOS 10 and native scroller

2016-10-06 Thread Peter TB Brett
On 06/10/2016 12:09, John Dixon wrote: Does the fix to the native scroller include having the scrolling items remain within the declared content rect, rather tha Yes. The ability to scroll in a phone app is more than a little important... any time-scale on 'as soon as possible' for

Re: iOS 10 and native scroller

2016-10-06 Thread John Dixon
gt; Sent: 06 October 2016 11:19 To: How to use LiveCode Subject: Re: iOS 10 and native scroller On 06/10/2016 10:58, tekne wrote: > I see the bug is already fixed with target release 8.1.2-rc-1 > When do you think we can have this release? > > The mobile picker doesn't work correctly

Re: iOS 10 and native scroller

2016-10-06 Thread Peter TB Brett
On 06/10/2016 10:58, tekne wrote: I see the bug is already fixed with target release 8.1.2-rc-1 When do you think we can have this release? The mobile picker doesn't work correctly with iOS10 and to solve we need to use Xcode 8 which is not supported in LC6 or LC7 anymore. So I can¹t upload

Re: iOS 10 and native scroller

2016-10-06 Thread tekne
rett <peter.br...@livecode.com> Sent: 28 September 2016 11:08 To: How to use LiveCode Subject: Re: iOS 10 and native scroller On 28/09/2016 06:59, Ludovic THEBAULT wrote: > to have a native scroller on field list i've made this : > > put my long field in a group > set t

Re: iOS 10 and native scroller

2016-09-28 Thread John Dixon
28 September 2016 11:08 To: How to use LiveCode Subject: Re: iOS 10 and native scroller On 28/09/2016 06:59, Ludovic THEBAULT wrote: > to have a native scroller on field list i've made this : > > put my long field in a group > set the size of the group and lock it > > it worked per

Re: iOS 10 and native scroller

2016-09-28 Thread Peter TB Brett
On 28/09/2016 06:59, Ludovic THEBAULT wrote: to have a native scroller on field list i’ve made this : put my long field in a group set the size of the group and lock it it worked perfectly until iOS 10. Now I see my text beyond group boundaries. I believe you are describing bug 17779 [1],