On 07/06/2016 12:11 PM, Sannyasin Brahmanathaswami wrote:
Plus I was recently scolded off list for reporting bugs that were actually my
ignorance.
Whoever did the scolding (you know who you are) did no service to you,
to the user base in general, and to LiveCode quality. If you think you
behalf of Mike
Kerner <mikeker...@roadrunner.com>
Reply-To: How LiveCode <use-livecode@lists.runrev.com>
Date: Wednesday, July 6, 2016 at 9:36 AM
To: How LiveCode <use-livecode@lists.runrev.com>
Subject: Re: Front and Back Scripts on Mobile
BR, why can't I just call you "4D wonk&q
Sannyasin Brahmanathaswami wrote:
> Richard wrote:
> That doesn't seem as much a documentation error as a Standalone
> Builder bug. Have you reported it?
>
> This seems to "elementary" that I could not imagine the team would
> not see this before release.
There are some regressions that mystify
one) then I bug report it.
>
> I assume you feel that we should be able add stack files on mobile… so, I
> will report it.
>
> BR
>
> Richard wrote:
>
> Subject: Re: Front and Back Scripts on Mobile
>
> but the button to add stack
> > files the standalon
a bit gun shy about reporting bugs
until I flog it to death on this list first. Once it stops moving (no more
replies from anyone) then I bug report it.
I assume you feel that we should be able add stack files on mobile… so, I will
report it.
BR
Richard wrote:
Subject: Re: Front and Ba
code@lists.runrev.com>
Subject: Re: Front and Back Scripts on Mobile
San,
I have only been paying light attention to this thread, so if I missed
this, please ignore. Have you checked to find out if something else is
silently killing your script cascade before it gets to the backscript?
___
On 7/5/2016 10:21 PM, Sannyasin Brahmanathaswami wrote:
Stack A home.livecode | card 1 | group "portal-links"
on open card
createScroller "portal-links"
Stack B surprise-me.livecode t| card 2 | group "surprise-links"
on open card
createScroller "surprise-links"
things improved
Sannyasin Brahmanathaswami wrote:
> Part of the solution is more examples/amd explanation(s) in the
> dictionary itself. For example, right now I'm struggling with getting
> a mobileCreateScroller to work from a backscript.
>
> I think it may do better using an external lc.livecodescript script
.com>
> Date: Tuesday, July 5, 2016 at 10:57 PM
> To: How LiveCode <use-livecode@lists.runrev.com>
> Subject: RE: Front and Back Scripts on Mobile
>
> On the LiveCode website there are a lot of lessons but they all dealing
> with
> different aspects how to do this or th
my iPhone…
BR
From: use-livecode <use-livecode-boun...@lists.runrev.com> on behalf of Erik
Beugelaar <ebeugel...@gmail.com>
Reply-To: How LiveCode <use-livecode@lists.runrev.com>
Date: Tuesday, July 5, 2016 at 10:57 PM
To: How LiveCode <use-livecode@lists.runrev.com>
S
...@lists.runrev.com] On Behalf
Of Ralph DiMola
Sent: woensdag 6 juli 2016 03:30
To: 'How to use LiveCode' <use-livecode@lists.runrev.com>
Subject: RE: Front and Back Scripts on Mobile
Richard Gaskin wrote:
why isn't it in the tin?
Maybe there should be a "MobileNative" property on
See other post… the dictionary says
Optional string to use to identify the control. The controlName must be unique
amongst all existing controls and cannot be an integer.
so I set the name of the group of links on
Stack A home.livecode | card 1 | group "portal-links"
on open card
behalf of Richard
Gaskin <ambassa...@fourthworld.com>
Reply-To: How LiveCode <use-livecode@lists.runrev.com>
Date: Tuesday, July 5, 2016 at 1:27 PM
To: How LiveCode <use-livecode@lists.runrev.com>
Subject: Re: Front and Back Scripts on Mobile
The downside is I have no idea why Braman
Richard Gaskin wrote:
why isn't it in the tin?
Maybe there should be a "MobileNative" property on a field. If set to true
then all that stuff we've talked about would be invoked. Setting the
vscrollbar to true would create the native scroller. When a field is not
locked(for input) then only a
Ralph DiMola wrote:
> In the beginning all this fuss to make a mobile scroller got LC
> mobile off the ground, but it seems to me that it's time to fold
> it into the LC field object.
The field part of it seems finally underway - that was the last of the
stretch goals for the latest crowd
Richard Gaskin wrote:
>why isn't it in the tin?
Maybe there should be a "MobileNative" property on a field. If set to true
then all that stuff we've talked about would be invoked. Setting the
vscrollbar to true would create the native scroller. When a field is not
locked(for input) then only a
Ralph DiMola wrote:
Thanks J! Yes exactly. I do all my coding around the LC field. When the user
enters data in the native field I then move it to the LC field and work on
it there. This allows IDE testing. Then when you start up the app set the
visible of the LC field to true if in IDE (JLG's
ssage-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of J. Landman Gay
Sent: Tuesday, July 05, 2016 7:15 PM
To: How to use LiveCode
Subject: Re: Front and Back Scripts on Mobile
If you assign a name to the native control, mobileControlTarget() returns it
instead
J. Landman Gay wrote:
> If you assign a name to the native control, mobileControlTarget()
> returns it instead of the number.
Ah, nice. Must have missed that in the docs. Thanks. After all these
years whenever I come across something called "ID" my instinctive
response is to treat it as a
If you assign a name to the native control, mobileControlTarget() returns
it instead of the number. It's a handy way to match up native controls to
their LC counterparts without keeping a reference list.
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software
Ralph DiMola wrote:
> This is what works for me
...
> on scrollerDidScroll hScrolled, vScrolled
>local ControlID
>--answer "Here!"
>try
> put mobileControlTarget() into ControlID
> set the vscroll of control ControlID of stack "xxx" to vscrolled
> set the
ices
rdim...@evergreeninfo.net
-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of
Sannyasin Brahmanathaswami
Sent: Tuesday, July 05, 2016 6:05 PM
To: How to use LiveCode
Subject: Re: Front and Back Scripts on Mobile
Hmmm, today it's not w
Sannyasin Brahmanathaswami wrote:
> Hmmm, today it's not working… not sure how to debug…
...
> on scrollerDidScroll hScrolled, vScrolled
>
> put mobileControlTarget() into tControlID
>
> set the vscroll of control tControlID to vscrolled
>
> pass scrollerDidScroll
>
> end scrollerDidScroll
>
>
ply-To: How LiveCode <use-livecode@lists.runrev.com>
Date: Saturday, July 2, 2016 at 8:47 AM
To: How LiveCode <use-livecode@lists.runrev.com>
Subject: Re: Front and Back Scripts on Mobile
I believe a more accurate description is that the scrollerDidScroll
message is sent to the *script*
On 7/4/2016 11:42 AM, Richard Gaskin wrote:
J. Landman Gay wrote:
On July 4, 2016 9:34:52 AM Richard Gaskin wrote:
On the desktop, a scrollable object is distinguished by having
scrollbars.
On mobile, of course, we don't want the scrollbars shown since that's
not how mobile scrolling
J. Landman Gay wrote:
> On July 4, 2016 9:34:52 AM Richard Gaskin wrote:
>
>> On the desktop, a scrollable object is distinguished by having
>> scrollbars.
>>
>> On mobile, of course, we don't want the scrollbars shown since that's
>> not how mobile scrolling interaction works there. But
On July 4, 2016 9:34:52 AM Richard Gaskin wrote:
On the desktop, a scrollable object is distinguished by having scrollbars.
On mobile, of course, we don't want the scrollbars shown since that's
not how mobile scrolling interaction works there. But development
Sannyasin Brahmanathaswami wrote:
> @Richard:
>
> Thanks… confirmed… today it is working, yesterday it was not… go
> figure. create scroller and scrollerdidscroll now in our backscript.
> awesome!
Once I got the hang of it I've been pretty pleased with LC's scroller
handling. And fortunately
m>
Reply-To: How LiveCode <use-livecode@lists.runrev.com>
Date: Saturday, July 2, 2016 at 8:47 AM
To: How LiveCode <use-livecode@lists.runrev.com>
Subject: Re: Front and Back Scripts on Mobile
I believe a more accurate description is that the scrollerDidScroll
message is sent to
Sannyasin Brahmanathaswami wrote:
> Ralph wrote:
>> I had this problem way back. Mark noted that that the scroller
>> messages are sent to the stack that created the scroller.
>
> Does it makes sense to file this as an enhancement request?
I believe a more accurate description is that the
Ralph wrote:
I had this problem way back. Mark noted that that the scroller messages are
sent to the stack that created the scroller.
Does it makes sense to file this as an enhancement request?
All modern CMV systems provide for a controller to push a single model across
many views. And
00:42
(GMT-05:00) To: How to use LiveCode <use-livecode@lists.runrev.com>
Subject: Re: Front and Back Scripts on Mobile
We are looking to use some back scripts on mobile.
If I add this to a backscript
command testMessagePath pMessage
answer pMessage with "OK"
end
t;Got it"
save and reload the stack… it works on desktop, but not on mobile
OTOH some other commands in the back script *are* firing… because we have some
set up functions that are not failing.
Are there caveats for using front and back scripts on mobile that we need
understand?
BR
t;Got it"
save and reload the stack… it works on desktop, but not on mobile
OTOH some other commands in the back script *are* firing… because we have some
set up functions that are not failing.
Are there caveats for using front and back scripts on mobile that we n
34 matches
Mail list logo