Re: Bug [15118] native scroller
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 am sure you will never forget to set the visible of a scroller to true, like i ever won´t forget to add that „pass savestackrequest“ thing. ;) Matthias Am 14.04.2015 um 14:17 schrieb John Dixon dixo...@hotmail.co.uk: 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 except that 'I am an idiot'... I have no excuse whatsoever for missing such a fundamental line as setting the visible of the 'scroller' to true. 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 missing line that caused me to think that the scroller in LC 6.7.4 LC 7.0.4 was not working and prompted me to file a 'bug' report... I apologise to Hanson, Sebastien and Panos for putting up with my 'bug' report, completely wasting their time and for getting me out of the 'massive' hole that I have manged to dig for myself... Gentlemen... I thank you.. John Dixon ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Bug [15118] native scroller
On 4/14/2015 11:23 AM, Richard Gaskin wrote: Is this obsolete? http://lessons.runrev.com/m/4069/l/94412-creating-a-native-scroller-to-scroll-a-field 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 to write the same lines of code over and over to instantiate every object as a mobile control that the docs suggest we do? The concept is that the content rect has to be larger than the visible area. One way to do that is to set the field height/width the same as its formattedHeight/width and then group it to provide a smaller viewing area. The other way is to set the content rect of the native scroller to the formattedrect of the field, and lock the visible field rect at a smaller size. You can still set the scroll of the field regardless of how much is visible at any time. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Bug [15118] native scroller
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 ambassa...@fourthworld.com wrote: 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 need to group a single field. Is this obsolete? http://lessons.runrev.com/m/4069/l/94412-creating-a-native-scroller-to-scroll-a-field 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 to write the same lines of code over and over to instantiate every object as a mobile control that the docs suggest we do? -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Bug [15118] native scroller
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 ambassa...@fourthworld.comhttp://www.FourthWorld.com William Prothero wrote: 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 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 need to group a single field. Is this obsolete? http://lessons.runrev.com/m/4069/l/94412-creating-a-native-scroller-to-scroll-a-field 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 to write the same lines of code over and over to instantiate every object as a mobile control that the docs suggest we do? ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Bug [15118] native scroller
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.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Bug [15118] native scroller
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 commands for every control you create. A library script or a shared handler is handy for that. Pass it a field reference and just call that. Do I remember right that LC is going to simplify this for us when Open Language happens? Or maybe it's a widget thing? If so, that may be why it hasn't been streamlined yet. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Bug [15118] native scroller
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 missing line that caused me to think that the scroller in LC 6.7.4 LC 7.0.4 was not working and prompted me to file a 'bug' report... I apologise to Hanson, Sebastien and Panos for putting up with my 'bug' report, completely wasting their time and for getting me out of the 'massive' hole that I have manged to dig for myself... That was very gentlemanly of you, but in all fairness I've always wondered why the engine doesn't just instantiate those for us. Now that I'm doing mobile work in earnest I found it tedious to create groups around fields, so I've been experimenting with having those dynamically created at runtime via script, and then calling the appropriate native instantiation calls. But to be honest it feels a little silly having to do that: the engine knows the rect of the object, and it knows the object is visible, and it knows the object is scrolling. If I can write a script to look for those and automatically instantiate scrollers as needed, is it really too hard for the engine to do? After all, scripts are run by the engine. Whingeing aside, there was another bit of good news from this thread - earlier I'd noted that we can't paste text from LiveCode into programs that expect styled text, and I got notice this morning that now the lead engineer, Mark Waddingham, is looking into that. Good to see progress like this. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
RE: Bug [15118] native scroller
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://www.ihouse.on-rev.com/showstuff/scrollgroupshot.png One just must remember to make the scroller visible in order to see the whole lot..:-) John Dixon On April 14, 2015 9:58:25 AM CDT, Richard Gaskin ambassa...@fourthworld.com 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. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Bug [15118] native scroller
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 need to group a single field. Is this obsolete? http://lessons.runrev.com/m/4069/l/94412-creating-a-native-scroller-to-scroll-a-field 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 to write the same lines of code over and over to instantiate every object as a mobile control that the docs suggest we do? -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Bug [15118] native scroller
On April 14, 2015 9:58:25 AM CDT, Richard Gaskin ambassa...@fourthworld.com 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. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Bug [15118] native scroller
Am 14.04.2015 um 14:17 schrieb John Dixon dixo...@hotmail.co.uk: 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 except that 'I am an idiot'... I have no excuse whatsoever for missing such a fundamental line as setting the visible of the 'scroller' to true. 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 missing line that caused me to think that the scroller in LC 6.7.4 LC 7.0.4 was not working and prompted me to file a 'bug' report... I apologise to Hanson, Sebastien and Panos for putting up with my 'bug' report, completely wasting their time and for getting me out of the 'massive' hole that I have manged to dig for myself... Gentlemen... I thank you.. John Dixon [Bug 15118] native scroller To: dixo...@hotmail.co.uk Panos Merakos changed bug 15118 What Removed Added Status CONFIRMED PENDING_AWAITING_FOLLOW_UP CC panos.mera...@livecode.com Comment # 9 on bug 15118 from Panos Merakos Hi John, We had a deeper look in the scripts of the sample stacks you have attached, and found the problem. You have not set the visible of the scroller to true, and this is why it does not scroll. This is what we did to resolve the issue: 1. In stack local directory copy.livecode: Go to card id 1011, and add the following line in the buildScroller handler (at the point where you set the scroller properties) iphoneControlSet scrollID, visible, true 2. In stacks textScroll.livecode and PicsHorz copy.livecode, this line already exists, and thus the scrollers work as expected. 3. In stack scroll704.livecode: Go to card id 1002, and add the following line in the buildScroller handler (at the point where you set the scroller properties): iphoneControlSet scrollID, visible, true Can you please let us know if this fixes the problem for you? Warmest regards, Panos -- You are receiving this mail because: You are on the CC list for the bug.You reported the bug. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
