9.5.1 should have the fix (or whatever it is named).
9.0.5 already has the fix.
Thanks,
Brian
On Oct 25, 2019, 10:44 PM -0400, Paul Looney via use-livecode
, wrote:
> So, to be fixed in 9.0.6?
>
>
> > On Oct 25, 2019, at 6:53 PM, Bob Sneidar via use-livecode
> > wrote:
> >
> > Nope my bad.
So, to be fixed in 9.0.6?
> On Oct 25, 2019, at 6:53 PM, Bob Sneidar via use-livecode
> wrote:
>
> Nope my bad. Not fixed in 9.5 yet.
>
> Bob S
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe,
Nope my bad. Not fixed in 9.5 yet.
Bob S
> On Oct 25, 2019, at 16:10 , Tom Glod via use-livecode
> wrote:
>
> any chance you are reading clipboard data?
>
> On Fri, Oct 25, 2019 at 6:57 PM Mark Wieder via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> On 10/25/19 3:07 PM,
True, but only because you can't give Apple its cut unless the app is signed.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On October 25, 2019 8:38:13 PM Richard Gaskin via use-livecode
wrote:
hh wrote:
> The new security hystery
hh wrote:
> The new security hystery will surprise you every few
> minutes when you really work on that OS.
Let me guess: If I give 30% of my income to Apple then all those nasty
warnings in my apps just go away.
#shakedown
--
Richard Gaskin
Fourth World Systems
Software Design and
> What fresh hell is this? Is this something all of our
> users will be seeing?
Yes. But this is only the camp fire before the hell.
The new security hystery will surprise you every few
minutes when you really work on that OS.
___
use-livecode
Thanks, Jacque.
Looking into this more deeply I believe it's not triggered by LC itself,
but by a companion app my client has written.
I'll suggest they sign that to make that abstract annoyance go away.
--
Richard Gaskin
Fourth World Systems
Jacqueline Landman Gay wrote:
Weird macOS
After installing LC 9.5 on macOS "Catalina", when I run it I get a
system alert I've never seen before:
"LiveCode Indy 9.5.0" wants access to
control "System Events". Allowing control
will provide access to documents and data
in "System Events", and to perform actions
within that app."
On 10/25/19 4:08 PM, Richard Gaskin via use-livecode wrote:
Searching for "LiveCode blog" recently turned up this nice site:
https://livecode-blogger.blogspot.com/
Try as I might, I couldn't turn up any identifying information about the
blogger. Anyone know who it is?
Looks like maxv to me.
I have no idea, but thats a great blog. Whoever it is, they are no slouch.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
any chance you are reading clipboard data?
On Fri, Oct 25, 2019 at 6:57 PM Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:
> On 10/25/19 3:07 PM, Jerry Jensen via use-livecode wrote:
> > Thanks Bob. I thought the red dot crashing was fixed in 9.0.5 and not
> yet put in 9.5
Searching for "LiveCode blog" recently turned up this nice site:
https://livecode-blogger.blogspot.com/
Try as I might, I couldn't turn up any identifying information about the
blogger. Anyone know who it is?
--
Richard Gaskin
Fourth World Systems
Software Design and Development for
On 10/25/19 3:07 PM, Jerry Jensen via use-livecode wrote:
Thanks Bob. I thought the red dot crashing was fixed in 9.0.5 and not yet put
in 9.5 until the next “imminent” release. No?
That is correct.
--
Mark Wieder
ahsoftw...@gmail.com
___
Thanks Bob. I thought the red dot crashing was fixed in 9.0.5 and not yet put
in 9.5 until the next “imminent” release. No?
.Jerry
> On Oct 25, 2019, at 3:04 PM, Bob Sneidar via use-livecode
> wrote:
>
> 9.5.0 Community. Sorry when it comes to info more is better. Usually. ;-)
> Also MacOS
The reason I think it might be red dot crashing is I have noticed that the red
dot is not always in sync with the line it is supposed to be pointing at,
typically when scrolling. It seems to correct itself, but then shortly after I
saw this while debugging a behavior and switching between
9.5.0 Community. Sorry when it comes to info more is better. Usually. ;-) Also
MacOS Mojave fully updated.
Bob S
> On Oct 25, 2019, at 14:59 , Jerry Jensen via use-livecode
> wrote:
>
> Which version of LC?
___
use-livecode mailing list
Which version of LC?
> On Oct 25, 2019, at 2:28 PM, Bob Sneidar via use-livecode
> wrote:
>
> Still getting red dot breakpoint crashes. This time when switching to the
> calling handler. Not a big deal for me just saying.
>
> Bob S
>
>
> ___
>
Just to inform you.
Once again a ("maintenance"?)-change was done without any
notification.
Livecodeshare/SampleStacks has a new size limit:
If you have a sample stack there that has size > 2.1 Mbyte
(probably 2048 Kbyte) then it downloads from
http://livecodeshare.runrev.com with zero Bytes or
Still getting red dot breakpoint crashes. This time when switching to the
calling handler. Not a big deal for me just saying.
Bob S
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and
hi Jacque
Yes, In the end Todd bit the bullet and did it with the native field on both
iOS and Android ... now for the testing and inevitable quirks.
this lesson gave initial food for thought
http://lessons.livecode.com/m/4069/l/29112-how-do-i-use-native-text-controls-on-mobile
But a newbie
I use to indicate where I am by answering something like "I'm entering in
handler XYZ", "I exit handler XYZ"
Sometime I use answering to know what is in a special Variable, an so on.
I's simple, but it woks, especially when I use several handlers.
Alain Vezina
Logilangue
> Le 25 oct. 2019 à
J,
Sorry I meant send this to you last time you asked and got sidetracked, then
spaced out and forgot. After creating the scroller do a send in time to a
handler to set the non-zero scroll. I use .5 seconds but less might work.
Ralph DiMola
IT Director
Evergreen Information Services
I am still struggling with native scroller alignment when the scroll
must be set to something other than zero. Since I've asked here twice
with little response, maybe I just need to know more about how scrollers
work under the hood. Panos? Anyone?
* If I set the vScroll or hScroll of a
its mostly for try routines so i'm using it like it
try
something
catch TheError
LogError TheError
end try
in LogError handler is where i read the correct line and item in the
executioncontexts.
On Fri, Oct 25, 2019 at 2:47 PM Bob Sneidar via use-livecode <
Item 2 of line -1 of the executionContexts
> On Oct 25, 2019, at 11:46 , Bob Sneidar wrote:
>
> Correction Item 2
>
>> On Oct 25, 2019, at 11:46 , Bob Sneidar wrote:
>>
>> Item 3
>>
>>
>>> On Oct 25, 2019, at 11:39 , Tom Glod via use-livecode
>>> wrote:
>>>
>>> Its for error handling
So Tom, do you need
return item 2 of line -2 of the executioncontexts
to be in every possible handler?
On Fri, 25 Oct 2019 at 19:40, Tom Glod via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Its for error handling ...I want my error handler to know which handler the
> error was in.
>
Correction Item 2
> On Oct 25, 2019, at 11:46 , Bob Sneidar wrote:
>
> Item 3
>
>
>> On Oct 25, 2019, at 11:39 , Tom Glod via use-livecode
>> wrote:
>>
>> Its for error handling ...I want my error handler to know which handler the
>> error was in.
>
Item 3
> On Oct 25, 2019, at 11:39 , Tom Glod via use-livecode
> wrote:
>
> Its for error handling ...I want my error handler to know which handler the
> error was in.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this
Its for error handling ...I want my error handler to know which handler the
error was in.
On Fri, Oct 25, 2019 at 2:37 PM Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
> executionContexts is way more useful.
>
> Bob S
>
>
> > On Oct 25, 2019, at 11:14 , Mark Wieder via
executionContexts is way more useful.
Bob S
> On Oct 25, 2019, at 11:14 , Mark Wieder via use-livecode
> wrote:
>
> On 10/25/19 11:00 AM, Richard Gaskin via use-livecode wrote:
>> Tom Glod wrote:
>> > But is there a function that I can call inside a handler that will
>> > tell me the name
On 10/25/19 11:44 AM, Lagi Pittas via use-livecode wrote:
Jacque, you do a lot of Android programming if memory serves - do you use
native all the time for text input
or are we just "holding it wrong"?
I use native fields almost all the time. If you write a generic handler
that calls
On 10/25/19 11:00 AM, Richard Gaskin via use-livecode wrote:
Tom Glod wrote:
> But is there a function that I can call inside a handler that will
> tell me the name of the handler?
I'm curious: what are you doing that needs this?
Not Tom, but...
I do this all the time when I need to
Tom Glod wrote:
> But is there a function that I can call inside a handler that will
> tell me the name of the handler?
I'm curious: what are you doing that needs this?
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
On Oct 25, 2019, at 10:32 AM, Tom Glod via use-livecode
wrote:
>
> Phil.NICE! ...everything seems like a no brainer in hindsight.
That actually came up in litigation over the patent for the shaving cream can.
The challenger claimed that it was too obvious, and not patentable.
The
Phil.NICE! ...everything seems like a no brainer in hindsight.
On Fri, Oct 25, 2019 at 1:29 PM Phil Davis via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Tom, param(0) contains the name of the handler you're in.
>
> on mouseUp
> put param(0)
> end mouseUp
>
> Would put
Awesome.. thank you gentlemen.
Wrote a function.
*function* WhatsMyHanderName
*return* item 2 of line -2 of the executioncontexts
*end* WhatsMyHanderName
On Fri, Oct 25, 2019 at 1:06 PM Peter Bogdanoff via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Have you looked at
Tom, param(0) contains the name of the handler you're in.
on mouseUp
put param(0)
end mouseUp
Would put into the message box:
mouseUp
Phil Davis
On 10/25/19 10:00 AM, Tom Glod via use-livecode wrote:
Hey you guys, I have searched high and low and I am pretty sure the answer
is no ,
Not always. Sometimes you don't want that. But you can't turn it off.
Brian Milby via use-livecode schreef op 25
oktober 2019 19:05:06 CEST:
>Probably a big advantage to using native fields on mobile is
>cut/copy/paste.
>
>Thanks,
>Brian
>On Oct 25, 2019, 12:46 PM -0400, Lagi Pittas via
executionContexts
Bob S
> On Oct 25, 2019, at 10:00 , Tom Glod via use-livecode
> wrote:
>
> Hey you guys, I have searched high and low and I am pretty sure the answer
> is no , but I wanted to make sure before I did a feature request and a
> workaround.
>
> But is there a function that I
Probably a big advantage to using native fields on mobile is cut/copy/paste.
Thanks,
Brian
On Oct 25, 2019, 12:46 PM -0400, Lagi Pittas via use-livecode
, wrote:
> We are working on an App that runs on IOS/Android and Windows so making
> sure
> the Codebase and elements/objects are as much the
Have you looked at executionContexts?
Peter
> On Oct 25, 2019, at 1:00 PM, Tom Glod via use-livecode
> wrote:
>
> Hey you guys, I have searched high and low and I am pretty sure the answer
> is no , but I wanted to make sure before I did a feature request and a
> workaround.
>
> But is there
Hey you guys, I have searched high and low and I am pretty sure the answer
is no , but I wanted to make sure before I did a feature request and a
workaround.
But is there a function that I can call inside a handler that will tell me
the name of the handler?
Just like the params() tells me the
We are working on an App that runs on IOS/Android and Windows so making
sure
the Codebase and elements/objects are as much the same on each platform is
important.
Even more important is that we use the same elements on all platforms
including LC fields that are much easier to use than native text
43 matches
Mail list logo
