Re: Bug [15118] native scroller

2015-04-14 Thread J. Landman Gay
On 4/14/2015 11:23 AM, Richard Gaskin wrote: Are there other cases where we don't really need to write the same lines of code over and over to instantiate every object as a mobile control that the docs suggest we do? Since all native controls are created dynamically, you do need to repeat the

Re: Bug [15118] native scroller

2015-04-14 Thread J. Landman Gay
On 4/14/2015 11:44 AM, Richard Gaskin wrote: But does the native field object have the appropriate scrolling behaviors when rendered on mobile (bounce-back/glow, etc.)? Yes. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperac

Re: Bug [15118] native scroller

2015-04-14 Thread J. Landman Gay
On 4/14/2015 11:23 AM, Richard Gaskin wrote: Is this obsolete? Does the LC field object take on the appropriate scrolling behavior when rendered on mobile? Are there other cases where we don't really need t

Re: Bug [15118] native scroller

2015-04-14 Thread Richard Gaskin
But does the native field object have the appropriate scrolling behaviors when rendered on mobile (bounce-back/glow, etc.)? -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web

Re: Bug [15118] native scroller

2015-04-14 Thread William Prothero
Richard: When I looked at the link you posted, the very last comment in the comments section had a question of whether the field really needed to be in a group. Elanor Buchanan answered that it was not necessary. Best, Bill > On Apr 14, 2015, at 9:23 AM, Richard Gaskin > wrote: > > J. Landman

Re: Bug [15118] native scroller

2015-04-14 Thread Richard Gaskin
J. Landman Gay wrote: > On April 14, 2015 9:58:25 AM CDT, Richard Gaskin wrote: > >> Now that I'm doing mobile work in earnest I found it tedious to >> create groups around fields, > > I've scrolled fields directly without grouping them in the past. > Unless something changed, I don't think you n

RE: Bug [15118] native scroller

2015-04-14 Thread John Dixon
Jacque.. You are correct about scrolling fields... I create a group and copy the required number of groups to a master group that I wish to display.. for example... show in the image below, I have a group that consists of 2 images, 2 fields... there are 140 of these that are scrolled.. http:

Re: Bug [15118] native scroller

2015-04-14 Thread J. Landman Gay
On April 14, 2015 9:58:25 AM CDT, Richard Gaskin wrote: >Now that I'm doing mobile work in earnest I found it tedious to create >groups around fields, I've scrolled fields directly without grouping them in the past. Unless something changed, I don't think you need to group a single field. -

Re: Bug [15118] native scroller

2015-04-14 Thread Matthias Rebbe | M-R-D
Don´t know, why my last post was empty… John, you´re not alone. I also ran into such situation. I reported a bug that sometimes LC5 did not attach the database drivers to the standalones, but LC 4 did. My fault was i forgot to add a „pass savestackrequest“ to the SaveStackRequest handler. I

Re: Bug [15118] native scroller

2015-04-14 Thread Richard Gaskin
John Dixon wrote: > I was absolutely convinced that I was correct, as I was using the > same code that is already in a stack on the Apple app store... I > must have deleted the line whilst preparing a facelift for the > app...:-( > >iphoneControlSet scrollID, "visible", true > > this is the

Re: Bug [15118] native scroller

2015-04-14 Thread J. Landman Gay
On April 14, 2015 7:17:27 AM CDT, John Dixon wrote: > >After having read your email, there is nothing I can say except that 'I >am an idiot'... A very gracious reply. But don't worry, you get several of those for free. It's only after repeated infractions that they take away your computer and m

Re: Bug [15118] native scroller

2015-04-14 Thread Matthias Rebbe | M-R-D
> Am 14.04.2015 um 14:17 schrieb John Dixon : > > > > > > > > > This is addressed to a number of members of the liveCode team in Edinburgh... > To three members of the team in particular... > > Hanson, Sebastien and Panos... > > After having read your email, there is nothing I can say