Re: Which git service suits a LiveCoder best?
On 4/23/20 9:04 PM, Brian Milby via use-livecode wrote: New dedicated repo is located at: https://github.com/bwmilby/scriptTracker Oh, cool. I'll change my git remote. -- Mark Wieder ahsoftw...@gmail.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: Which git service suits a LiveCoder best?
New dedicated repo is located at: https://github.com/bwmilby/scriptTracker Thanks, Brian On Apr 24, 2020, 12:02 AM -0400, Mark Wieder via use-livecode , wrote: > On 4/23/20 6:58 PM, Brian Milby via use-livecode wrote: > > My scriptTracker plugin is an easy way to get the scripts out as text files > > for use with git (binary stack stays the same, plugin can automatically > > export scripts on every save of the stack) > > Which, if you can deal with the sluggishness of livecodeshare, is at > http://livecodeshare.runrev.com/stack/874/Script-Tracker > > or > https://github.com/bwmilby/lc-misc > > -- > Mark Wieder > ahsoftw...@gmail.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: Which git service suits a LiveCoder best?
On 4/23/20 6:58 PM, Brian Milby via use-livecode wrote: My scriptTracker plugin is an easy way to get the scripts out as text files for use with git (binary stack stays the same, plugin can automatically export scripts on every save of the stack) Which, if you can deal with the sluggishness of livecodeshare, is at http://livecodeshare.runrev.com/stack/874/Script-Tracker or https://github.com/bwmilby/lc-misc -- Mark Wieder ahsoftw...@gmail.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: Which git service suits a LiveCoder best?
My scriptTracker plugin is an easy way to get the scripts out as text files for use with git (binary stack stays the same, plugin can automatically export scripts on every save of the stack) Thanks, Brian On Apr 23, 2020, 9:20 PM -0400, doc hawk via use-livecode , wrote: > Andreas announced, > > Thanks everyone for your feedback and insights. Nothing speaks against > > GitHub, it seems, so I’ll give that a try then. > > I’m curious though: *how* are you gong to do this? > > Don’t you need to reduce the stacks to text files first? > > > ___ > 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: Which git service suits a LiveCoder best?
Andreas announced, > Thanks everyone for your feedback and insights. Nothing speaks against > GitHub, it seems, so I’ll give that a try then. I’m curious though: *how* are you gong to do this? Don’t you need to reduce the stacks to text files first? ___ 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: Widget Properties
Hello Graham, Sorry if I missed this earlier but, what made you go with a button widget rather than just using a standard LiveCode button? — Scott > On Apr 23, 2020, at 9:41 AM, Graham Samuel via use-livecode > wrote: > > I am getting rather fed up with the widgets I’ve been trying to use for my > mobile app. For example, the iOS button widget (a press button, not a switch) > has so few properties that you can’t change the colour of the text in any way > I could see and sometimes mine turn out blue or red for no apparent reason. > Hoping that other properties were just not showing up, I tried > > put the properties of widget “myWidget” > > in the message box and got nothing, so I don’t know how to proceed. > > I also hate that the object doesn’t have a label separate from its name. I > would never recommend anyone to put spaces in names of objects for scripting, > but of course they’re essential for many kinds of label seen by a user, so > the two different strings which work in normal LC are essential, in my > opinion. > > Oh dear, this has some danger of becoming a rant… > > Graham > ___ > 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: Which git service suits a LiveCoder best?
Thanks everyone for your feedback and insights. Nothing speaks against GitHub, it seems, so I’ll give that a try then. Andreas ___ 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
Widget Properties
I am getting rather fed up with the widgets I’ve been trying to use for my mobile app. For example, the iOS button widget (a press button, not a switch) has so few properties that you can’t change the colour of the text in any way I could see and sometimes mine turn out blue or red for no apparent reason. Hoping that other properties were just not showing up, I tried put the properties of widget “myWidget” in the message box and got nothing, so I don’t know how to proceed. I also hate that the object doesn’t have a label separate from its name. I would never recommend anyone to put spaces in names of objects for scripting, but of course they’re essential for many kinds of label seen by a user, so the two different strings which work in normal LC are essential, in my opinion. Oh dear, this has some danger of becoming a rant… Graham ___ 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: Is there a general mobile picker available?
Thanks Klaus and Ben! It’s easy to miss stuff, then one feels stupid. I can’t immediately remember what an “options” menu is, or how to invoke one, so I’ll just go with a simple ‘mobilepick’ for now. Graba > On 23 Apr 2020, at 17:18, Ben Rubinstein via use-livecode > wrote: > > Also, a standard LiveCode "Options" menu renders as a native picker on iOS > (not sure about Android). This is convenient, because it works in a sensible > way on desktop, and in a native way on iOS. Of course, it looks like a shitty > motif button until the user touches it... > > On 23/04/2020 13:48, Klaus major-k via use-livecode wrote: >> Hi Graham, >>> Am 23.04.2020 um 14:39 schrieb Graham Samuel via use-livecode >>> : >>> >>> Another mobile question: >>> >>> We have a Native Date Picker, and a Native Time Picker, but what about a >>> picker where you construct your own picking list? I would like to use a >>> picker on iOS to replace radio buttons, but I don’t know a way to do it. >>> Have I just missed it, or isn’t it possible? >> you just missed it! :-) >> Check -> mobilepick >> in the dictionary, that will let you create your own list and let the user >> pick one! >>> Graham >> Best >> Klaus > > ___ > 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: Native Switch Button?
Hi Graham - I can't answer this in detail, but I have used the native switchbutton widget, a bit, without seeing any problem of the kind you describe. I'm catching the hiliteChanged message in the widget itself, not in the card script, for what that's worth. (By the way, it scales - it's just that the default size is probably a bit excessive.) On 23/04/2020 11:04, Graham Samuel via use-livecode wrote: To add to my query below, there’s something even more strange. In my beta app there is a card with three Native Switch Buttons on it (they all have different names). i have another test card, as described before, with its own switch. When a button script on yet another card executes a ‘go' to the 3-switch card, the hiliteChanged handler in the test card fires, even though the card isn’t open! Again, the switch on this card has a different name - I read somewhere that widget names have to be unique - but this CAN’T be expected behaviour, can it? I am about to issue a bug report, but it may take too long to get a recipe. Graham On 23 Apr 2020, at 11:28, Graham Samuel via use-livecode wrote: Is anyone using the Native Switch Button? It looks OK (a bit big on my iOS simulator, but it will do) and it works - although the insanity of spelling “highlight” two ways in the one object is apparent - but running an experiment just now in which I go to a card with such an on object on it and not much else, certainly nothing in the card script, a ‘hiliteChanged’ event is triggered even though AFAIKS the highlight (see what I did there?) hasn’t changed. Is this expected behaviour? I can’t really believe it, but as usual I can’t see what i’m doing wrong. I certainly don’t want the message to be triggered unless the user touches the screen or I deliberately change the state by script. Graham ___ 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: Is there a general mobile picker available?
Also, a standard LiveCode "Options" menu renders as a native picker on iOS (not sure about Android). This is convenient, because it works in a sensible way on desktop, and in a native way on iOS. Of course, it looks like a shitty motif button until the user touches it... On 23/04/2020 13:48, Klaus major-k via use-livecode wrote: Hi Graham, Am 23.04.2020 um 14:39 schrieb Graham Samuel via use-livecode : Another mobile question: We have a Native Date Picker, and a Native Time Picker, but what about a picker where you construct your own picking list? I would like to use a picker on iOS to replace radio buttons, but I don’t know a way to do it. Have I just missed it, or isn’t it possible? you just missed it! :-) Check -> mobilepick in the dictionary, that will let you create your own list and let the user pick one! Graham Best Klaus ___ 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: Mobile text input mystery
You're welcome, Graham - thanks for the follow up. I'll make sure we add a note about this simulator keyboard trick in the dictionary. Kind regards, Panos -- On Thu, 23 Apr 2020 at 15:33, Graham Samuel via use-livecode < use-livecode@lists.runrev.com> wrote: > Thanks a million, Panos, it all works! Apart from the simulator keyboard > trick, I can’t see immediately what I did wrong. Probably haven’t got time > to crawl over it now… obviously I can use this as a model in any part of > the app that needs it. > > Thanks again > > Graham > > > On 23 Apr 2020, at 13:39, panagiotis merakos via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > Hello Graham, > > > > The following works as expected for me: > > > > on opencard > > global gInputID > > if environment() = "mobile" then > > mobileControlCreate "input" -- so the user can type in > > put the result into gInputID > > answer "opening text field for input. ID created is:" && gInputID > > mobileControlSet gInputID, "rect", "114,135,163,158" > > mobileControlSet gInputID, "visible", "true" > > mobileControlSet gInputID, "opaque", "true" > > mobileControlSet gInputID, "borderstyle", "line" > > end if > > end opencard > > > > also I have added two buttons to test the other issues: > > > > script of button 1: > > > > on mouseup > > local tText > > global gInputID > > put mobileControlGet(gInputID,"text") into tText > > answer tText > > end mouseup > > > > > > script of button 2: > > > > on mouseUp pButtonNumber > > global gInputID > > mobileControlSet gInputID, "keyboardType", "numeric" > > mobileControlDo gInputID, "focus" > > end mouseUp > > > > Also, while testing the focus, I realised that you have to enable the > > setting "Toggle Software Keyboard" in the simulator menubar (Hardware -> > > Keyboard -> Toggle Software Keyboard). > > > > Important: Note that you have to FIRST click on the field with the mouse > to > > focus it, and THEN check this option, otherwise your choice will not have > > any effect. This might be a bug in the simulator app, but once you do > that, > > your choice of showing the soft keyboard will be remembered. > > > > So now, if you add some text to the field, it will be returned correctly > if > > you press the first button. Also, if you click on the second button, you > > should see a numeric soft keyboard appearing, and the field will get the > > focus. > > > > Hope this helps. > > > > Kind regards, > > Panos > > -- > > > > On Thu, 23 Apr 2020 at 14:03, panagiotis merakos > wrote: > > > >> Hello Graham, > >> > >> Oh, ignore my previous comment about mobileControlDo , > >> "focus", as this bug affected Android only. > >> > >> I'll try to reproduce the recipe here and see if I get the same problem. > >> > >> Kind regards, > >> Panos > >> -- > >> > >> > >> On Thu, 23 Apr 2020 at 13:54, panagiotis merakos > >> wrote: > >> > >>> Hello Graham, > >>> > >>> > >>> > >>> > >>> > >>> > >>> *> but despite executing> > mobileControlSet "FRadiusText", > >>> "keyboardType", "numeric"> mobileControlDo "FRadiusText", "focus"> > > >>> following what the LC Dictionary says , I do not see the soft > keyboard* > >>> > >>> This will not work in LC 9.5.1 - it is an old bug that is fixed in LC > 9.6 > >>> DP-3: > >>> > >>> https://github.com/livecode/livecode/pull/7259 > >>> > >>> *>>nor does a subsequent* > >>> > >>> *> mobileControlGet "FRadiusText", "text"> ever result in anything but > >>> empty even though I can see a text in the native field object.* > >>> > >>> Are you calling mobileControlGet "FRadiusText", "text" from the same > >>> handler that has created the mobile input field, or from a different > one? > >>> > >>> Kind regards, > >>> Panos > >>> -- > >>> > >>> On Wed, 22 Apr 2020 at 23:39, Graham Samuel via use-livecode < > >>> use-livecode@lists.runrev.com> wrote: > >>> > > > Sent from my iPad > > Begin forwarded message: > > > From: Graham Samuel > > Date: 22 April 2020 at 22:14:37 CEST > > To: Mark Waddingham > > Subject: Re: Mobile text input mystery > > > > Thanks Mark. Although making the field opaque wasn’t enough, giving > it a black border worked and I can now see it. I can edit it with the > mouse, and I can even put something in it with > > > > mobileControlSet "FRadiusText", "text", "1.0" > > > > but despite executing > > > > mobileControlSet "FRadiusText", "keyboardType", "numeric" > > mobileControlDo "FRadiusText", "focus" > > > > following what the LC Dictionary says , I do not see the soft > keyboard, nor does a subsequent > > > > mobileControlGet "FRadiusText", "text" > > > > ever result in anything but empty even though I can see a text in the > native field object. > > > > But I can’t keep asking questions. I’ll just tinker as usual and hope > to get a result. > > > > Thanks again > > > > G
Re: Is there a general mobile picker available?
Hi Graham, > Am 23.04.2020 um 14:39 schrieb Graham Samuel via use-livecode > : > > Another mobile question: > > We have a Native Date Picker, and a Native Time Picker, but what about a > picker where you construct your own picking list? I would like to use a > picker on iOS to replace radio buttons, but I don’t know a way to do it. Have > I just missed it, or isn’t it possible? you just missed it! :-) Check -> mobilepick in the dictionary, that will let you create your own list and let the user pick one! > Graham Best Klaus -- Klaus Major https://www.major-k.de kl...@major-k.de ___ 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
Is there a general mobile picker available?
Another mobile question: We have a Native Date Picker, and a Native Time Picker, but what about a picker where you construct your own picking list? I would like to use a picker on iOS to replace radio buttons, but I don’t know a way to do it. Have I just missed it, or isn’t it possible? Graham ___ 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: Mobile text input mystery
Thanks a million, Panos, it all works! Apart from the simulator keyboard trick, I can’t see immediately what I did wrong. Probably haven’t got time to crawl over it now… obviously I can use this as a model in any part of the app that needs it. Thanks again Graham > On 23 Apr 2020, at 13:39, panagiotis merakos via use-livecode > wrote: > > Hello Graham, > > The following works as expected for me: > > on opencard > global gInputID > if environment() = "mobile" then > mobileControlCreate "input" -- so the user can type in > put the result into gInputID > answer "opening text field for input. ID created is:" && gInputID > mobileControlSet gInputID, "rect", "114,135,163,158" > mobileControlSet gInputID, "visible", "true" > mobileControlSet gInputID, "opaque", "true" > mobileControlSet gInputID, "borderstyle", "line" > end if > end opencard > > also I have added two buttons to test the other issues: > > script of button 1: > > on mouseup > local tText > global gInputID > put mobileControlGet(gInputID,"text") into tText > answer tText > end mouseup > > > script of button 2: > > on mouseUp pButtonNumber > global gInputID > mobileControlSet gInputID, "keyboardType", "numeric" > mobileControlDo gInputID, "focus" > end mouseUp > > Also, while testing the focus, I realised that you have to enable the > setting "Toggle Software Keyboard" in the simulator menubar (Hardware -> > Keyboard -> Toggle Software Keyboard). > > Important: Note that you have to FIRST click on the field with the mouse to > focus it, and THEN check this option, otherwise your choice will not have > any effect. This might be a bug in the simulator app, but once you do that, > your choice of showing the soft keyboard will be remembered. > > So now, if you add some text to the field, it will be returned correctly if > you press the first button. Also, if you click on the second button, you > should see a numeric soft keyboard appearing, and the field will get the > focus. > > Hope this helps. > > Kind regards, > Panos > -- > > On Thu, 23 Apr 2020 at 14:03, panagiotis merakos wrote: > >> Hello Graham, >> >> Oh, ignore my previous comment about mobileControlDo , >> "focus", as this bug affected Android only. >> >> I'll try to reproduce the recipe here and see if I get the same problem. >> >> Kind regards, >> Panos >> -- >> >> >> On Thu, 23 Apr 2020 at 13:54, panagiotis merakos >> wrote: >> >>> Hello Graham, >>> >>> >>> >>> >>> >>> >>> *> but despite executing> > mobileControlSet "FRadiusText", >>> "keyboardType", "numeric"> mobileControlDo "FRadiusText", "focus"> > >>> following what the LC Dictionary says , I do not see the soft keyboard* >>> >>> This will not work in LC 9.5.1 - it is an old bug that is fixed in LC 9.6 >>> DP-3: >>> >>> https://github.com/livecode/livecode/pull/7259 >>> >>> *>>nor does a subsequent* >>> >>> *> mobileControlGet "FRadiusText", "text"> ever result in anything but >>> empty even though I can see a text in the native field object.* >>> >>> Are you calling mobileControlGet "FRadiusText", "text" from the same >>> handler that has created the mobile input field, or from a different one? >>> >>> Kind regards, >>> Panos >>> -- >>> >>> On Wed, 22 Apr 2020 at 23:39, Graham Samuel via use-livecode < >>> use-livecode@lists.runrev.com> wrote: >>> Sent from my iPad Begin forwarded message: > From: Graham Samuel > Date: 22 April 2020 at 22:14:37 CEST > To: Mark Waddingham > Subject: Re: Mobile text input mystery > > Thanks Mark. Although making the field opaque wasn’t enough, giving it a black border worked and I can now see it. I can edit it with the mouse, and I can even put something in it with > > mobileControlSet "FRadiusText", "text", "1.0" > > but despite executing > > mobileControlSet "FRadiusText", "keyboardType", "numeric" > mobileControlDo "FRadiusText", "focus" > > following what the LC Dictionary says , I do not see the soft keyboard, nor does a subsequent > > mobileControlGet "FRadiusText", "text" > > ever result in anything but empty even though I can see a text in the native field object. > > But I can’t keep asking questions. I’ll just tinker as usual and hope to get a result. > > Thanks again > > Graham > >> On 22 Apr 2020, at 19:52, Mark Waddingham wrote: >> >>> On 2020-04-22 18:38, Graham Samuel wrote: >>> Reading your response, Mark, I didn't feel so bad, since the LC >>> Dictionary says for example about mobileControlSet >>> syntax: mobileControlSet idOrName, PropertyName, value >>> and later explains >>> idOrName - the id or name of the control >>> So I therefore saw the two ways of referring to the control as >>> apparently interchangeable. >> >> It is - apologies - the engine does
Re: Mobile text input mystery
Sorry Panos, my short email crossed with your long one. I am trying all your suggestions now! Graham > On 23 Apr 2020, at 13:39, panagiotis merakos via use-livecode > wrote: > > Hello Graham, > > The following works as expected for me: > > on opencard > global gInputID > if environment() = "mobile" then > mobileControlCreate "input" -- so the user can type in > put the result into gInputID > answer "opening text field for input. ID created is:" && gInputID > mobileControlSet gInputID, "rect", "114,135,163,158" > mobileControlSet gInputID, "visible", "true" > mobileControlSet gInputID, "opaque", "true" > mobileControlSet gInputID, "borderstyle", "line" > end if > end opencard > > also I have added two buttons to test the other issues: > > script of button 1: > > on mouseup > local tText > global gInputID > put mobileControlGet(gInputID,"text") into tText > answer tText > end mouseup > > > script of button 2: > > on mouseUp pButtonNumber > global gInputID > mobileControlSet gInputID, "keyboardType", "numeric" > mobileControlDo gInputID, "focus" > end mouseUp > > Also, while testing the focus, I realised that you have to enable the > setting "Toggle Software Keyboard" in the simulator menubar (Hardware -> > Keyboard -> Toggle Software Keyboard). > > Important: Note that you have to FIRST click on the field with the mouse to > focus it, and THEN check this option, otherwise your choice will not have > any effect. This might be a bug in the simulator app, but once you do that, > your choice of showing the soft keyboard will be remembered. > > So now, if you add some text to the field, it will be returned correctly if > you press the first button. Also, if you click on the second button, you > should see a numeric soft keyboard appearing, and the field will get the > focus. > > Hope this helps. > > Kind regards, > Panos > -- > > On Thu, 23 Apr 2020 at 14:03, panagiotis merakos wrote: > >> Hello Graham, >> >> Oh, ignore my previous comment about mobileControlDo , >> "focus", as this bug affected Android only. >> >> I'll try to reproduce the recipe here and see if I get the same problem. >> >> Kind regards, >> Panos >> -- >> >> >> On Thu, 23 Apr 2020 at 13:54, panagiotis merakos >> wrote: >> >>> Hello Graham, >>> >>> >>> >>> >>> >>> >>> *> but despite executing> > mobileControlSet "FRadiusText", >>> "keyboardType", "numeric"> mobileControlDo "FRadiusText", "focus"> > >>> following what the LC Dictionary says , I do not see the soft keyboard* >>> >>> This will not work in LC 9.5.1 - it is an old bug that is fixed in LC 9.6 >>> DP-3: >>> >>> https://github.com/livecode/livecode/pull/7259 >>> >>> *>>nor does a subsequent* >>> >>> *> mobileControlGet "FRadiusText", "text"> ever result in anything but >>> empty even though I can see a text in the native field object.* >>> >>> Are you calling mobileControlGet "FRadiusText", "text" from the same >>> handler that has created the mobile input field, or from a different one? >>> >>> Kind regards, >>> Panos >>> -- >>> >>> On Wed, 22 Apr 2020 at 23:39, Graham Samuel via use-livecode < >>> use-livecode@lists.runrev.com> wrote: >>> Sent from my iPad Begin forwarded message: > From: Graham Samuel > Date: 22 April 2020 at 22:14:37 CEST > To: Mark Waddingham > Subject: Re: Mobile text input mystery > > Thanks Mark. Although making the field opaque wasn’t enough, giving it a black border worked and I can now see it. I can edit it with the mouse, and I can even put something in it with > > mobileControlSet "FRadiusText", "text", "1.0" > > but despite executing > > mobileControlSet "FRadiusText", "keyboardType", "numeric" > mobileControlDo "FRadiusText", "focus" > > following what the LC Dictionary says , I do not see the soft keyboard, nor does a subsequent > > mobileControlGet "FRadiusText", "text" > > ever result in anything but empty even though I can see a text in the native field object. > > But I can’t keep asking questions. I’ll just tinker as usual and hope to get a result. > > Thanks again > > Graham > >> On 22 Apr 2020, at 19:52, Mark Waddingham wrote: >> >>> On 2020-04-22 18:38, Graham Samuel wrote: >>> Reading your response, Mark, I didn't feel so bad, since the LC >>> Dictionary says for example about mobileControlSet >>> syntax: mobileControlSet idOrName, PropertyName, value >>> and later explains >>> idOrName - the id or name of the control >>> So I therefore saw the two ways of referring to the control as >>> apparently interchangeable. >> >> It is - apologies - the engine does look up both by id or name... >> >> Do you see something if you also set the 'text' property? >> >> There's also the 'borderStyle' property too. >>
Re: Mobile text input mystery
Just tried it after switching to LC9.6.0 DP4 - no change. I’m keen to see if you can indeed reproduce it. Graham > On 23 Apr 2020, at 13:03, panagiotis merakos via use-livecode > wrote: > > Hello Graham, > > Oh, ignore my previous comment about mobileControlDo , "focus", > as this bug affected Android only. > > I'll try to reproduce the recipe here and see if I get the same problem. > > Kind regards, > Panos > -- > > > On Thu, 23 Apr 2020 at 13:54, panagiotis merakos wrote: > >> Hello Graham, >> >> >> >> >> >> >> *> but despite executing> > mobileControlSet "FRadiusText", >> "keyboardType", "numeric"> mobileControlDo "FRadiusText", "focus"> > >> following what the LC Dictionary says , I do not see the soft keyboard* >> >> This will not work in LC 9.5.1 - it is an old bug that is fixed in LC 9.6 >> DP-3: >> >> https://github.com/livecode/livecode/pull/7259 >> >> *>>nor does a subsequent* >> >> *> mobileControlGet "FRadiusText", "text"> ever result in anything but >> empty even though I can see a text in the native field object.* >> >> Are you calling mobileControlGet "FRadiusText", "text" from the same >> handler that has created the mobile input field, or from a different one? >> >> Kind regards, >> Panos >> -- >> >> On Wed, 22 Apr 2020 at 23:39, Graham Samuel via use-livecode < >> use-livecode@lists.runrev.com> wrote: >> >>> >>> >>> Sent from my iPad >>> >>> Begin forwarded message: >>> From: Graham Samuel Date: 22 April 2020 at 22:14:37 CEST To: Mark Waddingham Subject: Re: Mobile text input mystery Thanks Mark. Although making the field opaque wasn’t enough, giving it >>> a black border worked and I can now see it. I can edit it with the mouse, >>> and I can even put something in it with mobileControlSet "FRadiusText", "text", "1.0" but despite executing mobileControlSet "FRadiusText", "keyboardType", "numeric" mobileControlDo "FRadiusText", "focus" following what the LC Dictionary says , I do not see the soft >>> keyboard, nor does a subsequent mobileControlGet "FRadiusText", "text" ever result in anything but empty even though I can see a text in the >>> native field object. But I can’t keep asking questions. I’ll just tinker as usual and hope >>> to get a result. Thanks again Graham > On 22 Apr 2020, at 19:52, Mark Waddingham wrote: > >> On 2020-04-22 18:38, Graham Samuel wrote: >> Reading your response, Mark, I didn't feel so bad, since the LC >> Dictionary says for example about mobileControlSet >> syntax: mobileControlSet idOrName, PropertyName, value >> and later explains >> idOrName - the id or name of the control >> So I therefore saw the two ways of referring to the control as >> apparently interchangeable. > > It is - apologies - the engine does look up both by id or name... > > Do you see something if you also set the 'text' property? > > There's also the 'borderStyle' property too. > > My hunch is that something is there, but the background color is the >>> same as the card, the border style is none and it has no content so it >>> looks like nothing is there? > > Warmest Regards, > > Mark. > > -- > Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ > LiveCode: Everyone can create apps >>> ___ >>> 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 ___ 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: Mobile text input mystery
Hello Graham, The following works as expected for me: on opencard global gInputID if environment() = "mobile" then mobileControlCreate "input" -- so the user can type in put the result into gInputID answer "opening text field for input. ID created is:" && gInputID mobileControlSet gInputID, "rect", "114,135,163,158" mobileControlSet gInputID, "visible", "true" mobileControlSet gInputID, "opaque", "true" mobileControlSet gInputID, "borderstyle", "line" end if end opencard also I have added two buttons to test the other issues: script of button 1: on mouseup local tText global gInputID put mobileControlGet(gInputID,"text") into tText answer tText end mouseup script of button 2: on mouseUp pButtonNumber global gInputID mobileControlSet gInputID, "keyboardType", "numeric" mobileControlDo gInputID, "focus" end mouseUp Also, while testing the focus, I realised that you have to enable the setting "Toggle Software Keyboard" in the simulator menubar (Hardware -> Keyboard -> Toggle Software Keyboard). Important: Note that you have to FIRST click on the field with the mouse to focus it, and THEN check this option, otherwise your choice will not have any effect. This might be a bug in the simulator app, but once you do that, your choice of showing the soft keyboard will be remembered. So now, if you add some text to the field, it will be returned correctly if you press the first button. Also, if you click on the second button, you should see a numeric soft keyboard appearing, and the field will get the focus. Hope this helps. Kind regards, Panos -- On Thu, 23 Apr 2020 at 14:03, panagiotis merakos wrote: > Hello Graham, > > Oh, ignore my previous comment about mobileControlDo , > "focus", as this bug affected Android only. > > I'll try to reproduce the recipe here and see if I get the same problem. > > Kind regards, > Panos > -- > > > On Thu, 23 Apr 2020 at 13:54, panagiotis merakos > wrote: > >> Hello Graham, >> >> >> >> >> >> >> *> but despite executing> > mobileControlSet "FRadiusText", >> "keyboardType", "numeric"> mobileControlDo "FRadiusText", "focus"> > >> following what the LC Dictionary says , I do not see the soft keyboard* >> >> This will not work in LC 9.5.1 - it is an old bug that is fixed in LC 9.6 >> DP-3: >> >> https://github.com/livecode/livecode/pull/7259 >> >> *>>nor does a subsequent* >> >> *> mobileControlGet "FRadiusText", "text"> ever result in anything but >> empty even though I can see a text in the native field object.* >> >> Are you calling mobileControlGet "FRadiusText", "text" from the same >> handler that has created the mobile input field, or from a different one? >> >> Kind regards, >> Panos >> -- >> >> On Wed, 22 Apr 2020 at 23:39, Graham Samuel via use-livecode < >> use-livecode@lists.runrev.com> wrote: >> >>> >>> >>> Sent from my iPad >>> >>> Begin forwarded message: >>> >>> > From: Graham Samuel >>> > Date: 22 April 2020 at 22:14:37 CEST >>> > To: Mark Waddingham >>> > Subject: Re: Mobile text input mystery >>> > >>> > Thanks Mark. Although making the field opaque wasn’t enough, giving >>> it a black border worked and I can now see it. I can edit it with the >>> mouse, and I can even put something in it with >>> > >>> > mobileControlSet "FRadiusText", "text", "1.0" >>> > >>> > but despite executing >>> > >>> > mobileControlSet "FRadiusText", "keyboardType", "numeric" >>> > mobileControlDo "FRadiusText", "focus" >>> > >>> > following what the LC Dictionary says , I do not see the soft >>> keyboard, nor does a subsequent >>> > >>> > mobileControlGet "FRadiusText", "text" >>> > >>> > ever result in anything but empty even though I can see a text in the >>> native field object. >>> > >>> > But I can’t keep asking questions. I’ll just tinker as usual and hope >>> to get a result. >>> > >>> > Thanks again >>> > >>> > Graham >>> > >>> >> On 22 Apr 2020, at 19:52, Mark Waddingham wrote: >>> >> >>> >>> On 2020-04-22 18:38, Graham Samuel wrote: >>> >>> Reading your response, Mark, I didn't feel so bad, since the LC >>> >>> Dictionary says for example about mobileControlSet >>> >>> syntax: mobileControlSet idOrName, PropertyName, value >>> >>> and later explains >>> >>> idOrName - the id or name of the control >>> >>> So I therefore saw the two ways of referring to the control as >>> >>> apparently interchangeable. >>> >> >>> >> It is - apologies - the engine does look up both by id or name... >>> >> >>> >> Do you see something if you also set the 'text' property? >>> >> >>> >> There's also the 'borderStyle' property too. >>> >> >>> >> My hunch is that something is there, but the background color is the >>> same as the card, the border style is none and it has no content so it >>> looks like nothing is there? >>> >> >>> >> Warmest Regards, >>> >> >>> >> Mark. >>> >> >>> >> -- >>> >> Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ >>> >> LiveCode: Everyone can create apps >>> >
Re: Mobile text input mystery
Hello Graham, Oh, ignore my previous comment about mobileControlDo , "focus", as this bug affected Android only. I'll try to reproduce the recipe here and see if I get the same problem. Kind regards, Panos -- On Thu, 23 Apr 2020 at 13:54, panagiotis merakos wrote: > Hello Graham, > > > > > > > *> but despite executing> > mobileControlSet "FRadiusText", > "keyboardType", "numeric"> mobileControlDo "FRadiusText", "focus"> > > following what the LC Dictionary says , I do not see the soft keyboard* > > This will not work in LC 9.5.1 - it is an old bug that is fixed in LC 9.6 > DP-3: > > https://github.com/livecode/livecode/pull/7259 > > *>>nor does a subsequent* > > *> mobileControlGet "FRadiusText", "text"> ever result in anything but > empty even though I can see a text in the native field object.* > > Are you calling mobileControlGet "FRadiusText", "text" from the same > handler that has created the mobile input field, or from a different one? > > Kind regards, > Panos > -- > > On Wed, 22 Apr 2020 at 23:39, Graham Samuel via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> >> >> Sent from my iPad >> >> Begin forwarded message: >> >> > From: Graham Samuel >> > Date: 22 April 2020 at 22:14:37 CEST >> > To: Mark Waddingham >> > Subject: Re: Mobile text input mystery >> > >> > Thanks Mark. Although making the field opaque wasn’t enough, giving it >> a black border worked and I can now see it. I can edit it with the mouse, >> and I can even put something in it with >> > >> > mobileControlSet "FRadiusText", "text", "1.0" >> > >> > but despite executing >> > >> > mobileControlSet "FRadiusText", "keyboardType", "numeric" >> > mobileControlDo "FRadiusText", "focus" >> > >> > following what the LC Dictionary says , I do not see the soft >> keyboard, nor does a subsequent >> > >> > mobileControlGet "FRadiusText", "text" >> > >> > ever result in anything but empty even though I can see a text in the >> native field object. >> > >> > But I can’t keep asking questions. I’ll just tinker as usual and hope >> to get a result. >> > >> > Thanks again >> > >> > Graham >> > >> >> On 22 Apr 2020, at 19:52, Mark Waddingham wrote: >> >> >> >>> On 2020-04-22 18:38, Graham Samuel wrote: >> >>> Reading your response, Mark, I didn't feel so bad, since the LC >> >>> Dictionary says for example about mobileControlSet >> >>> syntax: mobileControlSet idOrName, PropertyName, value >> >>> and later explains >> >>> idOrName - the id or name of the control >> >>> So I therefore saw the two ways of referring to the control as >> >>> apparently interchangeable. >> >> >> >> It is - apologies - the engine does look up both by id or name... >> >> >> >> Do you see something if you also set the 'text' property? >> >> >> >> There's also the 'borderStyle' property too. >> >> >> >> My hunch is that something is there, but the background color is the >> same as the card, the border style is none and it has no content so it >> looks like nothing is there? >> >> >> >> Warmest Regards, >> >> >> >> Mark. >> >> >> >> -- >> >> Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ >> >> LiveCode: Everyone can create apps >> > >> ___ >> 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: Mobile text input mystery
Hello Graham, *> but despite executing> > mobileControlSet "FRadiusText", "keyboardType", "numeric"> mobileControlDo "FRadiusText", "focus"> > following what the LC Dictionary says , I do not see the soft keyboard* This will not work in LC 9.5.1 - it is an old bug that is fixed in LC 9.6 DP-3: https://github.com/livecode/livecode/pull/7259 *>>nor does a subsequent* *> mobileControlGet "FRadiusText", "text"> ever result in anything but empty even though I can see a text in the native field object.* Are you calling mobileControlGet "FRadiusText", "text" from the same handler that has created the mobile input field, or from a different one? Kind regards, Panos -- On Wed, 22 Apr 2020 at 23:39, Graham Samuel via use-livecode < use-livecode@lists.runrev.com> wrote: > > > Sent from my iPad > > Begin forwarded message: > > > From: Graham Samuel > > Date: 22 April 2020 at 22:14:37 CEST > > To: Mark Waddingham > > Subject: Re: Mobile text input mystery > > > > Thanks Mark. Although making the field opaque wasn’t enough, giving it > a black border worked and I can now see it. I can edit it with the mouse, > and I can even put something in it with > > > > mobileControlSet "FRadiusText", "text", "1.0" > > > > but despite executing > > > > mobileControlSet "FRadiusText", "keyboardType", "numeric" > > mobileControlDo "FRadiusText", "focus" > > > > following what the LC Dictionary says , I do not see the soft keyboard, > nor does a subsequent > > > > mobileControlGet "FRadiusText", "text" > > > > ever result in anything but empty even though I can see a text in the > native field object. > > > > But I can’t keep asking questions. I’ll just tinker as usual and hope to > get a result. > > > > Thanks again > > > > Graham > > > >> On 22 Apr 2020, at 19:52, Mark Waddingham wrote: > >> > >>> On 2020-04-22 18:38, Graham Samuel wrote: > >>> Reading your response, Mark, I didn't feel so bad, since the LC > >>> Dictionary says for example about mobileControlSet > >>> syntax: mobileControlSet idOrName, PropertyName, value > >>> and later explains > >>> idOrName - the id or name of the control > >>> So I therefore saw the two ways of referring to the control as > >>> apparently interchangeable. > >> > >> It is - apologies - the engine does look up both by id or name... > >> > >> Do you see something if you also set the 'text' property? > >> > >> There's also the 'borderStyle' property too. > >> > >> My hunch is that something is there, but the background color is the > same as the card, the border style is none and it has no content so it > looks like nothing is there? > >> > >> Warmest Regards, > >> > >> Mark. > >> > >> -- > >> Mark Waddingham ~ m...@livecode.com ~ http://www.livecode.com/ > >> LiveCode: Everyone can create apps > > > ___ > 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: Native Switch Button?
To add to my query below, there’s something even more strange. In my beta app there is a card with three Native Switch Buttons on it (they all have different names). i have another test card, as described before, with its own switch. When a button script on yet another card executes a ‘go' to the 3-switch card, the hiliteChanged handler in the test card fires, even though the card isn’t open! Again, the switch on this card has a different name - I read somewhere that widget names have to be unique - but this CAN’T be expected behaviour, can it? I am about to issue a bug report, but it may take too long to get a recipe. Graham > On 23 Apr 2020, at 11:28, Graham Samuel via use-livecode > wrote: > > Is anyone using the Native Switch Button? It looks OK (a bit big on my iOS > simulator, but it will do) and it works - although the insanity of spelling > “highlight” two ways in the one object is apparent - but running an > experiment just now in which I go to a card with such an on object on it and > not much else, certainly nothing in the card script, a ‘hiliteChanged’ event > is triggered even though AFAIKS the highlight (see what I did there?) hasn’t > changed. > > Is this expected behaviour? I can’t really believe it, but as usual I can’t > see what i’m doing wrong. I certainly don’t want the message to be triggered > unless the user touches the screen or I deliberately change the state by > script. > > Graham > ___ > 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
Native Switch Button?
Is anyone using the Native Switch Button? It looks OK (a bit big on my iOS simulator, but it will do) and it works - although the insanity of spelling “highlight” two ways in the one object is apparent - but running an experiment just now in which I go to a card with such an on object on it and not much else, certainly nothing in the card script, a ‘hiliteChanged’ event is triggered even though AFAIKS the highlight (see what I did there?) hasn’t changed. Is this expected behaviour? I can’t really believe it, but as usual I can’t see what i’m doing wrong. I certainly don’t want the message to be triggered unless the user touches the screen or I deliberately change the state by script. Graham ___ 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
