Re: disabled buttons still receive events, they just process them, later?
Exactly 37 years. I remember because I started learning HC when my son was born in order to take my mind off diapers. If I remember, we can commiserate . -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On February 21, 2024 8:14:19 PM Mike Kerner via use-livecode wrote: pfft there is zero chance of that it's been, what 37 years? man, i'm so old. On Wed, Feb 21, 2024 at 8:35 PM Stephen Barncard via use-livecode < use-livecode@lists.runrev.com> wrote: "there's still stuff to learn." . and remember . -- Stephen Barncard - Sebastopol Ca. USA - mixstream.org On Wed, Feb 21, 2024 at 5:24 PM Mike Kerner via use-livecode < use-livecode@lists.runrev.com> wrote: > thanks, jacque & mark > it's amazing that even after...a really long time...there's still stuff to > learn. > > On Wed, Feb 21, 2024 at 5:16 PM Mark Waddingham via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > It’s because of the wait - ‘blocking’ waits (those which aren’t ‘with > > messages’) queue any (low level) events so they are handled at the next > > wait (in this case the global one the engine does implicitly when there > are > > no handlers executing). > > > > Flushing events after the wait as Jacque suggests will ensure they aren’t > > there to handle. > > > > Warmest Regards. > > > > Mark. > > > > Sent from my iPhone > > > > > On 21 Feb 2024, at 21:59, Mike Kerner via use-livecode < > > use-livecode@lists.runrev.com> wrote: > > > > > > i did. > > > i have both a button, and a power button. > > > script: > > > > > > *local* count > > > > > > *on* mouseUp > > > > > > *if* the disabled of me *then* *put* cr & "disabled" after msg > > > > > > *add* 1 to count > > > > > > *set* the enabled of me to false > > > > > > *put* count > > > > > > *wait* 2 second > > > > > > *set* the enabled of me to true > > > > > > *end* mouseUp > > > > > >> On Wed, Feb 21, 2024 at 4:47 PM Craig Newman via use-livecode < > > >> use-livecode@lists.runrev.com> wrote: > > >> > > >> Mike. > > >> > > >> In a new stack I placed a button with this: > > >> > > >> on mouseUp > > >> beep 2 > > >> end mouseUp > > >> > > >> If I click on the button I hear two clicks. I disabled the button and > > >> clicked on it. I enabled the button. No clicks. I did this all by > hand. > > Did > > >> you? > > >> > > >> Craig > > >> > > >>> On Feb 21, 2024, at 4:07 PM, Mike Kerner via use-livecode < > > >> use-livecode@lists.runrev.com> wrote: > > >>> > > >>> alright, i'm a little surprised to notice this: > > >>> i have a button. i disabled the button. > > >>> then i clicked on the button > > >>> then i re-enabled the button > > >>> the click, from the period while the button was disabled, is received > > and > > >>> processed by the button. > > >>> that seems problematic, to me. how would one cause clicks to be > > >> discarded, > > >>> permanently? hide the button? overlay it with a transparent control > > that > > >>> will absorb and ignore the clicks? > > >>> > > >>> -- > > >>> On the first day, God created the heavens and the Earth > > >>> On the second day, God created the oceans. > > >>> On the third day, God put the animals on hold for a few hours, > > >>> and did a little diving. > > >>> And God said, "This is good." > > >>> ___ > > >>> 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 > > >> > > > > > > > > > -- > > > On the first day, God created the heavens and the Earth > > > On the second day, God created the oceans. > > > On the third day, God put the animals on hold for a few hours, > > > and did a little diving. > > > And God said, "This is good." > > > ___ > > > 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 > > > > > -- > On the first day, God created the heavens and the Earth > On the second day, God created the oceans. > On the third day, God put the animals on hold for a few hours, >and did a little diving. > And God said, "This is good." >
Re: disabled buttons still receive events, they just process them, later?
pfft there is zero chance of that it's been, what 37 years? man, i'm so old. On Wed, Feb 21, 2024 at 8:35 PM Stephen Barncard via use-livecode < use-livecode@lists.runrev.com> wrote: > "there's still stuff to > learn." > > . and remember . > -- > Stephen Barncard - Sebastopol Ca. USA - > mixstream.org > > > On Wed, Feb 21, 2024 at 5:24 PM Mike Kerner via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > thanks, jacque & mark > > it's amazing that even after...a really long time...there's still stuff > to > > learn. > > > > On Wed, Feb 21, 2024 at 5:16 PM Mark Waddingham via use-livecode < > > use-livecode@lists.runrev.com> wrote: > > > > > It’s because of the wait - ‘blocking’ waits (those which aren’t ‘with > > > messages’) queue any (low level) events so they are handled at the next > > > wait (in this case the global one the engine does implicitly when there > > are > > > no handlers executing). > > > > > > Flushing events after the wait as Jacque suggests will ensure they > aren’t > > > there to handle. > > > > > > Warmest Regards. > > > > > > Mark. > > > > > > Sent from my iPhone > > > > > > > On 21 Feb 2024, at 21:59, Mike Kerner via use-livecode < > > > use-livecode@lists.runrev.com> wrote: > > > > > > > > i did. > > > > i have both a button, and a power button. > > > > script: > > > > > > > > *local* count > > > > > > > > *on* mouseUp > > > > > > > > *if* the disabled of me *then* *put* cr & "disabled" after msg > > > > > > > > *add* 1 to count > > > > > > > > *set* the enabled of me to false > > > > > > > > *put* count > > > > > > > > *wait* 2 second > > > > > > > > *set* the enabled of me to true > > > > > > > > *end* mouseUp > > > > > > > >> On Wed, Feb 21, 2024 at 4:47 PM Craig Newman via use-livecode < > > > >> use-livecode@lists.runrev.com> wrote: > > > >> > > > >> Mike. > > > >> > > > >> In a new stack I placed a button with this: > > > >> > > > >> on mouseUp > > > >> beep 2 > > > >> end mouseUp > > > >> > > > >> If I click on the button I hear two clicks. I disabled the button > and > > > >> clicked on it. I enabled the button. No clicks. I did this all by > > hand. > > > Did > > > >> you? > > > >> > > > >> Craig > > > >> > > > >>> On Feb 21, 2024, at 4:07 PM, Mike Kerner via use-livecode < > > > >> use-livecode@lists.runrev.com> wrote: > > > >>> > > > >>> alright, i'm a little surprised to notice this: > > > >>> i have a button. i disabled the button. > > > >>> then i clicked on the button > > > >>> then i re-enabled the button > > > >>> the click, from the period while the button was disabled, is > received > > > and > > > >>> processed by the button. > > > >>> that seems problematic, to me. how would one cause clicks to be > > > >> discarded, > > > >>> permanently? hide the button? overlay it with a transparent control > > > that > > > >>> will absorb and ignore the clicks? > > > >>> > > > >>> -- > > > >>> On the first day, God created the heavens and the Earth > > > >>> On the second day, God created the oceans. > > > >>> On the third day, God put the animals on hold for a few hours, > > > >>> and did a little diving. > > > >>> And God said, "This is good." > > > >>> ___ > > > >>> 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 > > > >> > > > > > > > > > > > > -- > > > > On the first day, God created the heavens and the Earth > > > > On the second day, God created the oceans. > > > > On the third day, God put the animals on hold for a few hours, > > > > and did a little diving. > > > > And God said, "This is good." > > > > ___ > > > > 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 > > > > > > > > > -- > > On the first day, God created the heavens and the Earth > > On the second day, God created the oceans. > > On the third day, God put the animals on hold for a few hours, > >and did a little diving. > > And God said, "This is good." > > ___ > >
Re: disabled buttons still receive events, they just process them, later?
"there's still stuff to learn." . and remember . -- Stephen Barncard - Sebastopol Ca. USA - mixstream.org On Wed, Feb 21, 2024 at 5:24 PM Mike Kerner via use-livecode < use-livecode@lists.runrev.com> wrote: > thanks, jacque & mark > it's amazing that even after...a really long time...there's still stuff to > learn. > > On Wed, Feb 21, 2024 at 5:16 PM Mark Waddingham via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > It’s because of the wait - ‘blocking’ waits (those which aren’t ‘with > > messages’) queue any (low level) events so they are handled at the next > > wait (in this case the global one the engine does implicitly when there > are > > no handlers executing). > > > > Flushing events after the wait as Jacque suggests will ensure they aren’t > > there to handle. > > > > Warmest Regards. > > > > Mark. > > > > Sent from my iPhone > > > > > On 21 Feb 2024, at 21:59, Mike Kerner via use-livecode < > > use-livecode@lists.runrev.com> wrote: > > > > > > i did. > > > i have both a button, and a power button. > > > script: > > > > > > *local* count > > > > > > *on* mouseUp > > > > > > *if* the disabled of me *then* *put* cr & "disabled" after msg > > > > > > *add* 1 to count > > > > > > *set* the enabled of me to false > > > > > > *put* count > > > > > > *wait* 2 second > > > > > > *set* the enabled of me to true > > > > > > *end* mouseUp > > > > > >> On Wed, Feb 21, 2024 at 4:47 PM Craig Newman via use-livecode < > > >> use-livecode@lists.runrev.com> wrote: > > >> > > >> Mike. > > >> > > >> In a new stack I placed a button with this: > > >> > > >> on mouseUp > > >> beep 2 > > >> end mouseUp > > >> > > >> If I click on the button I hear two clicks. I disabled the button and > > >> clicked on it. I enabled the button. No clicks. I did this all by > hand. > > Did > > >> you? > > >> > > >> Craig > > >> > > >>> On Feb 21, 2024, at 4:07 PM, Mike Kerner via use-livecode < > > >> use-livecode@lists.runrev.com> wrote: > > >>> > > >>> alright, i'm a little surprised to notice this: > > >>> i have a button. i disabled the button. > > >>> then i clicked on the button > > >>> then i re-enabled the button > > >>> the click, from the period while the button was disabled, is received > > and > > >>> processed by the button. > > >>> that seems problematic, to me. how would one cause clicks to be > > >> discarded, > > >>> permanently? hide the button? overlay it with a transparent control > > that > > >>> will absorb and ignore the clicks? > > >>> > > >>> -- > > >>> On the first day, God created the heavens and the Earth > > >>> On the second day, God created the oceans. > > >>> On the third day, God put the animals on hold for a few hours, > > >>> and did a little diving. > > >>> And God said, "This is good." > > >>> ___ > > >>> 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 > > >> > > > > > > > > > -- > > > On the first day, God created the heavens and the Earth > > > On the second day, God created the oceans. > > > On the third day, God put the animals on hold for a few hours, > > > and did a little diving. > > > And God said, "This is good." > > > ___ > > > 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 > > > > > -- > On the first day, God created the heavens and the Earth > On the second day, God created the oceans. > On the third day, God put the animals on hold for a few hours, >and did a little diving. > And God said, "This is good." > ___ > 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: sideloading updates to mobile
thanks, jlg. that's kind-of what i was thinking. On Wed, Feb 21, 2024 at 4:58 PM J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > I've done this for several mobile apps. As long as the updates only reside > in the app's sandboxed container, even the App Store doesn't care. > > Basically, I put a short text file on the server listing the update > version(s) of the file(s), one per line if they are all different. Every > stack in the app suite has a custom property named cVersion. If necessary > you can also add the download URL to the same line. On launch, the app > downloads and parses the text to see if the server version is different > from the installed one. If so, it uses "put URL into URL > path>" to download and save the the updates to the mobile documents > folder, > overwriting the old ones. > > It's pretty simple, if I understand what you need correctly. I also store > other info in the the text file occasionally, such as a text string > describing the updates so I can show an answer dialog if I want the user > to > agree or decline the update (which will reappear on the next launch if > they > decline.) > > Sample text file is usually something like this: > >Stack 1 https://www.domain.com/updates/stack1.livecode >Stack 2 https://www.domain.com/updates/stack2.livecode >.. >This update provides new functionality and bug fixes. > > If you don't want to scan each stack for its cVersion, you can keep a text > file in the mobile documents folder that lists the current versions so you > can easily compare that to the one on the server. After updating the > stacks, update the stored text file as well. > > If updates are mandatory, just skip the comparisons entirely and > force-download the updates. If only some of the stacks should be updated, > omit the ones that don't need to be updated from the server file. > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > On February 21, 2024 12:53:25 PM Mike Kerner via use-livecode > wrote: > > > right - no updating the engine + runtime in this scenario, just the > > stacks + scripts, and perhaps plugins. > > we are going to continue to only privately distribute to our corporate > > clients, so the app store won't be part of the equation. that does not > mean > > that apple won't object, though (but, i believe the rules for privately > > distributed apps are much more lenient than for app store apps - at > least, > > they have been for us, up until now) > > > > On Wed, Feb 21, 2024 at 12:53 PM Klaus major-k via use-livecode < > > use-livecode@lists.runrev.com> wrote: > > > >> Hi Mike, > >> > >> > Am 21.02.2024 um 18:47 schrieb Mike Kerner via use-livecode < > >> use-livecode@lists.runrev.com>: > >> > > >> > sorry that i was not clear. we've been using private deploys since > around > >> > 2010, using airlaunch to generate the bundle, and then uploading to a > >> > private url. that's not what i meant. > >> > i'm talking about updating/patching an existing app, in place. the > >> devices > >> > are in single-app mode, so we would either have to pay for mdm and > then > >> use > >> > that service to push app updates, OR, if we didn't use mdm, we could > have > >> > the app pull the update and apply it. > >> > i can kind-of guess how to make it work, but i'm sure there are a > couple > >> of > >> > tricks that i don't want to have to figure out, if someone else has > >> already > >> > figured it out. > >> > >> you could use the "splashscreen" approach to update one or more stacks, > >> but that will > >> of course only work if you do not want to update the actual > engine/runtime. > >> > >> However I'm not sure if Apple will allow this, no problem on Android > >> however. > >> > >> > >> Best > >> > >> Klaus > >> > >> -- > >> Klaus Major > >> https://www.major-k.de > >> https://www.major-k.de/bass > >> 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 > >> > > > > > > -- > > On the first day, God created the heavens and the Earth > > On the second day, God created the oceans. > > On the third day, God put the animals on hold for a few hours, > > and did a little diving. > > And God said, "This is good." > > ___ > > 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: >
Re: disabled buttons still receive events, they just process them, later?
thanks, jacque & mark it's amazing that even after...a really long time...there's still stuff to learn. On Wed, Feb 21, 2024 at 5:16 PM Mark Waddingham via use-livecode < use-livecode@lists.runrev.com> wrote: > It’s because of the wait - ‘blocking’ waits (those which aren’t ‘with > messages’) queue any (low level) events so they are handled at the next > wait (in this case the global one the engine does implicitly when there are > no handlers executing). > > Flushing events after the wait as Jacque suggests will ensure they aren’t > there to handle. > > Warmest Regards. > > Mark. > > Sent from my iPhone > > > On 21 Feb 2024, at 21:59, Mike Kerner via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > i did. > > i have both a button, and a power button. > > script: > > > > *local* count > > > > *on* mouseUp > > > > *if* the disabled of me *then* *put* cr & "disabled" after msg > > > > *add* 1 to count > > > > *set* the enabled of me to false > > > > *put* count > > > > *wait* 2 second > > > > *set* the enabled of me to true > > > > *end* mouseUp > > > >> On Wed, Feb 21, 2024 at 4:47 PM Craig Newman via use-livecode < > >> use-livecode@lists.runrev.com> wrote: > >> > >> Mike. > >> > >> In a new stack I placed a button with this: > >> > >> on mouseUp > >> beep 2 > >> end mouseUp > >> > >> If I click on the button I hear two clicks. I disabled the button and > >> clicked on it. I enabled the button. No clicks. I did this all by hand. > Did > >> you? > >> > >> Craig > >> > >>> On Feb 21, 2024, at 4:07 PM, Mike Kerner via use-livecode < > >> use-livecode@lists.runrev.com> wrote: > >>> > >>> alright, i'm a little surprised to notice this: > >>> i have a button. i disabled the button. > >>> then i clicked on the button > >>> then i re-enabled the button > >>> the click, from the period while the button was disabled, is received > and > >>> processed by the button. > >>> that seems problematic, to me. how would one cause clicks to be > >> discarded, > >>> permanently? hide the button? overlay it with a transparent control > that > >>> will absorb and ignore the clicks? > >>> > >>> -- > >>> On the first day, God created the heavens and the Earth > >>> On the second day, God created the oceans. > >>> On the third day, God put the animals on hold for a few hours, > >>> and did a little diving. > >>> And God said, "This is good." > >>> ___ > >>> 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 > >> > > > > > > -- > > On the first day, God created the heavens and the Earth > > On the second day, God created the oceans. > > On the third day, God put the animals on hold for a few hours, > > and did a little diving. > > And God said, "This is good." > > ___ > > 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 > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." ___ 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: disabled buttons still receive events, they just process them, later?
It’s because of the wait - ‘blocking’ waits (those which aren’t ‘with messages’) queue any (low level) events so they are handled at the next wait (in this case the global one the engine does implicitly when there are no handlers executing). Flushing events after the wait as Jacque suggests will ensure they aren’t there to handle. Warmest Regards. Mark. Sent from my iPhone > On 21 Feb 2024, at 21:59, Mike Kerner via use-livecode > wrote: > > i did. > i have both a button, and a power button. > script: > > *local* count > > *on* mouseUp > > *if* the disabled of me *then* *put* cr & "disabled" after msg > > *add* 1 to count > > *set* the enabled of me to false > > *put* count > > *wait* 2 second > > *set* the enabled of me to true > > *end* mouseUp > >> On Wed, Feb 21, 2024 at 4:47 PM Craig Newman via use-livecode < >> use-livecode@lists.runrev.com> wrote: >> >> Mike. >> >> In a new stack I placed a button with this: >> >> on mouseUp >> beep 2 >> end mouseUp >> >> If I click on the button I hear two clicks. I disabled the button and >> clicked on it. I enabled the button. No clicks. I did this all by hand. Did >> you? >> >> Craig >> >>> On Feb 21, 2024, at 4:07 PM, Mike Kerner via use-livecode < >> use-livecode@lists.runrev.com> wrote: >>> >>> alright, i'm a little surprised to notice this: >>> i have a button. i disabled the button. >>> then i clicked on the button >>> then i re-enabled the button >>> the click, from the period while the button was disabled, is received and >>> processed by the button. >>> that seems problematic, to me. how would one cause clicks to be >> discarded, >>> permanently? hide the button? overlay it with a transparent control that >>> will absorb and ignore the clicks? >>> >>> -- >>> On the first day, God created the heavens and the Earth >>> On the second day, God created the oceans. >>> On the third day, God put the animals on hold for a few hours, >>> and did a little diving. >>> And God said, "This is good." >>> ___ >>> 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 >> > > > -- > On the first day, God created the heavens and the Earth > On the second day, God created the oceans. > On the third day, God put the animals on hold for a few hours, > and did a little diving. > And God said, "This is good." > ___ > 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: disabled buttons still receive events, they just process them, later?
That seems a little odd, I haven't noticed that. But one way to block the
messages is to use flushEvents() in the button script:
flushEvents("mouseDown")
flushEvents("mouseUp")
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On February 21, 2024 3:09:44 PM Mike Kerner via use-livecode
wrote:
alright, i'm a little surprised to notice this:
i have a button. i disabled the button.
then i clicked on the button
then i re-enabled the button
the click, from the period while the button was disabled, is received and
processed by the button.
that seems problematic, to me. how would one cause clicks to be discarded,
permanently? hide the button? overlay it with a transparent control that
will absorb and ignore the clicks?
--
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
and did a little diving.
And God said, "This is good."
___
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: disabled buttons still receive events, they just process them, later?
i did. i have both a button, and a power button. script: *local* count *on* mouseUp *if* the disabled of me *then* *put* cr & "disabled" after msg *add* 1 to count *set* the enabled of me to false *put* count *wait* 2 second *set* the enabled of me to true *end* mouseUp On Wed, Feb 21, 2024 at 4:47 PM Craig Newman via use-livecode < use-livecode@lists.runrev.com> wrote: > Mike. > > In a new stack I placed a button with this: > > on mouseUp > beep 2 > end mouseUp > > If I click on the button I hear two clicks. I disabled the button and > clicked on it. I enabled the button. No clicks. I did this all by hand. Did > you? > > Craig > > > On Feb 21, 2024, at 4:07 PM, Mike Kerner via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > alright, i'm a little surprised to notice this: > > i have a button. i disabled the button. > > then i clicked on the button > > then i re-enabled the button > > the click, from the period while the button was disabled, is received and > > processed by the button. > > that seems problematic, to me. how would one cause clicks to be > discarded, > > permanently? hide the button? overlay it with a transparent control that > > will absorb and ignore the clicks? > > > > -- > > On the first day, God created the heavens and the Earth > > On the second day, God created the oceans. > > On the third day, God put the animals on hold for a few hours, > > and did a little diving. > > And God said, "This is good." > > ___ > > 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 > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." ___ 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: sideloading updates to mobile
I've done this for several mobile apps. As long as the updates only reside in the app's sandboxed container, even the App Store doesn't care. Basically, I put a short text file on the server listing the update version(s) of the file(s), one per line if they are all different. Every stack in the app suite has a custom property named cVersion. If necessary you can also add the download URL to the same line. On launch, the app downloads and parses the text to see if the server version is different from the installed one. If so, it uses "put URL into URL path>" to download and save the the updates to the mobile documents folder, overwriting the old ones. It's pretty simple, if I understand what you need correctly. I also store other info in the the text file occasionally, such as a text string describing the updates so I can show an answer dialog if I want the user to agree or decline the update (which will reappear on the next launch if they decline.) Sample text file is usually something like this: Stack 1 https://www.domain.com/updates/stack1.livecode Stack 2 https://www.domain.com/updates/stack2.livecode .. This update provides new functionality and bug fixes. If you don't want to scan each stack for its cVersion, you can keep a text file in the mobile documents folder that lists the current versions so you can easily compare that to the one on the server. After updating the stacks, update the stored text file as well. If updates are mandatory, just skip the comparisons entirely and force-download the updates. If only some of the stacks should be updated, omit the ones that don't need to be updated from the server file. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On February 21, 2024 12:53:25 PM Mike Kerner via use-livecode wrote: right - no updating the engine + runtime in this scenario, just the stacks + scripts, and perhaps plugins. we are going to continue to only privately distribute to our corporate clients, so the app store won't be part of the equation. that does not mean that apple won't object, though (but, i believe the rules for privately distributed apps are much more lenient than for app store apps - at least, they have been for us, up until now) On Wed, Feb 21, 2024 at 12:53 PM Klaus major-k via use-livecode < use-livecode@lists.runrev.com> wrote: Hi Mike, > Am 21.02.2024 um 18:47 schrieb Mike Kerner via use-livecode < use-livecode@lists.runrev.com>: > > sorry that i was not clear. we've been using private deploys since around > 2010, using airlaunch to generate the bundle, and then uploading to a > private url. that's not what i meant. > i'm talking about updating/patching an existing app, in place. the devices > are in single-app mode, so we would either have to pay for mdm and then use > that service to push app updates, OR, if we didn't use mdm, we could have > the app pull the update and apply it. > i can kind-of guess how to make it work, but i'm sure there are a couple of > tricks that i don't want to have to figure out, if someone else has already > figured it out. you could use the "splashscreen" approach to update one or more stacks, but that will of course only work if you do not want to update the actual engine/runtime. However I'm not sure if Apple will allow this, no problem on Android however. Best Klaus -- Klaus Major https://www.major-k.de https://www.major-k.de/bass 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 -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." ___ 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: disabled buttons still receive events, they just process them, later?
Mike. In a new stack I placed a button with this: on mouseUp beep 2 end mouseUp If I click on the button I hear two clicks. I disabled the button and clicked on it. I enabled the button. No clicks. I did this all by hand. Did you? Craig > On Feb 21, 2024, at 4:07 PM, Mike Kerner via use-livecode > wrote: > > alright, i'm a little surprised to notice this: > i have a button. i disabled the button. > then i clicked on the button > then i re-enabled the button > the click, from the period while the button was disabled, is received and > processed by the button. > that seems problematic, to me. how would one cause clicks to be discarded, > permanently? hide the button? overlay it with a transparent control that > will absorb and ignore the clicks? > > -- > On the first day, God created the heavens and the Earth > On the second day, God created the oceans. > On the third day, God put the animals on hold for a few hours, > and did a little diving. > And God said, "This is good." > ___ > 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
disabled buttons still receive events, they just process them, later?
alright, i'm a little surprised to notice this: i have a button. i disabled the button. then i clicked on the button then i re-enabled the button the click, from the period while the button was disabled, is received and processed by the button. that seems problematic, to me. how would one cause clicks to be discarded, permanently? hide the button? overlay it with a transparent control that will absorb and ignore the clicks? -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." ___ 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: sideloading updates to mobile
Hi Mike, > Am 21.02.2024 um 20:17 schrieb Mike Kerner via use-livecode > : > > mobile device management: > https://en.wikipedia.org/wiki/Mobile_device_management > it's like testflight on steroids. in our case, it would enable us to force > app (and even os) updates on devices that are locked into single-app mode > >>> i guess the other option would be to roll an mdm server >> sorry, but what does "mdm" mean? thank you! Best Klaus -- Klaus Major https://www.major-k.de https://www.major-k.de/bass 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
Re: sideloading updates to mobile
mobile device management: https://en.wikipedia.org/wiki/Mobile_device_management it's like testflight on steroids. in our case, it would enable us to force app (and even os) updates on devices that are locked into single-app mode On Wed, Feb 21, 2024 at 1:57 PM Klaus major-k via use-livecode < use-livecode@lists.runrev.com> wrote: > Am 21.02.2024 um 19:51 schrieb Mike Kerner via use-livecode < > use-livecode@lists.runrev.com>: > > > > i guess the other option would be to roll an mdm server > > sorry, but what does "mdm" mean? > > -- > Klaus Major > https://www.major-k.de > https://www.major-k.de/bass > 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 > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." ___ 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: sideloading updates to mobile
Am 21.02.2024 um 19:51 schrieb Mike Kerner via use-livecode : > > i guess the other option would be to roll an mdm server sorry, but what does "mdm" mean? -- Klaus Major https://www.major-k.de https://www.major-k.de/bass 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
Re: sideloading updates to mobile
i guess the other option would be to roll an mdm server On Wed, Feb 21, 2024 at 1:50 PM Mike Kerner wrote: > right - no updating the engine + runtime in this scenario, just the > stacks + scripts, and perhaps plugins. > we are going to continue to only privately distribute to our corporate > clients, so the app store won't be part of the equation. that does not mean > that apple won't object, though (but, i believe the rules for privately > distributed apps are much more lenient than for app store apps - at least, > they have been for us, up until now) > > On Wed, Feb 21, 2024 at 12:53 PM Klaus major-k via use-livecode < > use-livecode@lists.runrev.com> wrote: > >> Hi Mike, >> >> > Am 21.02.2024 um 18:47 schrieb Mike Kerner via use-livecode < >> use-livecode@lists.runrev.com>: >> > >> > sorry that i was not clear. we've been using private deploys since >> around >> > 2010, using airlaunch to generate the bundle, and then uploading to a >> > private url. that's not what i meant. >> > i'm talking about updating/patching an existing app, in place. the >> devices >> > are in single-app mode, so we would either have to pay for mdm and then >> use >> > that service to push app updates, OR, if we didn't use mdm, we could >> have >> > the app pull the update and apply it. >> > i can kind-of guess how to make it work, but i'm sure there are a >> couple of >> > tricks that i don't want to have to figure out, if someone else has >> already >> > figured it out. >> >> you could use the "splashscreen" approach to update one or more stacks, >> but that will >> of course only work if you do not want to update the actual >> engine/runtime. >> >> However I'm not sure if Apple will allow this, no problem on Android >> however. >> >> >> Best >> >> Klaus >> >> -- >> Klaus Major >> https://www.major-k.de >> https://www.major-k.de/bass >> 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 >> > > > -- > On the first day, God created the heavens and the Earth > On the second day, God created the oceans. > On the third day, God put the animals on hold for a few hours, >and did a little diving. > And God said, "This is good." > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." ___ 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: sideloading updates to mobile
right - no updating the engine + runtime in this scenario, just the stacks + scripts, and perhaps plugins. we are going to continue to only privately distribute to our corporate clients, so the app store won't be part of the equation. that does not mean that apple won't object, though (but, i believe the rules for privately distributed apps are much more lenient than for app store apps - at least, they have been for us, up until now) On Wed, Feb 21, 2024 at 12:53 PM Klaus major-k via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi Mike, > > > Am 21.02.2024 um 18:47 schrieb Mike Kerner via use-livecode < > use-livecode@lists.runrev.com>: > > > > sorry that i was not clear. we've been using private deploys since around > > 2010, using airlaunch to generate the bundle, and then uploading to a > > private url. that's not what i meant. > > i'm talking about updating/patching an existing app, in place. the > devices > > are in single-app mode, so we would either have to pay for mdm and then > use > > that service to push app updates, OR, if we didn't use mdm, we could have > > the app pull the update and apply it. > > i can kind-of guess how to make it work, but i'm sure there are a couple > of > > tricks that i don't want to have to figure out, if someone else has > already > > figured it out. > > you could use the "splashscreen" approach to update one or more stacks, > but that will > of course only work if you do not want to update the actual engine/runtime. > > However I'm not sure if Apple will allow this, no problem on Android > however. > > > Best > > Klaus > > -- > Klaus Major > https://www.major-k.de > https://www.major-k.de/bass > 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 > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." ___ 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: sideloading updates to mobile
Hi Mike, > Am 21.02.2024 um 18:47 schrieb Mike Kerner via use-livecode > : > > sorry that i was not clear. we've been using private deploys since around > 2010, using airlaunch to generate the bundle, and then uploading to a > private url. that's not what i meant. > i'm talking about updating/patching an existing app, in place. the devices > are in single-app mode, so we would either have to pay for mdm and then use > that service to push app updates, OR, if we didn't use mdm, we could have > the app pull the update and apply it. > i can kind-of guess how to make it work, but i'm sure there are a couple of > tricks that i don't want to have to figure out, if someone else has already > figured it out. you could use the "splashscreen" approach to update one or more stacks, but that will of course only work if you do not want to update the actual engine/runtime. However I'm not sure if Apple will allow this, no problem on Android however. Best Klaus -- Klaus Major https://www.major-k.de https://www.major-k.de/bass 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
Re: sideloading updates to mobile
sorry that i was not clear. we've been using private deploys since around 2010, using airlaunch to generate the bundle, and then uploading to a private url. that's not what i meant. i'm talking about updating/patching an existing app, in place. the devices are in single-app mode, so we would either have to pay for mdm and then use that service to push app updates, OR, if we didn't use mdm, we could have the app pull the update and apply it. i can kind-of guess how to make it work, but i'm sure there are a couple of tricks that i don't want to have to figure out, if someone else has already figured it out. ___ 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: sideloading updates to mobile
Sideloading to iOS itself is fairly easy, even easier with Jacque’s wonderful tool AirLaunch (which allows you to post a link online for the end-user to visit and install from w/o being on-site). The biggest hurdle I have found is that you must first obtain the UDID of the specific device you want to side load to AND THEN create a new Provisioning Profile in the Apple Developer portal which includes that test device before you build. Without going through that process first you can build and submit to Apple using TestFlight which makes the update available to non-UDID obtained devices but is subject to the standard Apple approval process (which has taken between 4 hours and 2 weeks for me to pass over the years). - Andrew Bell > anyone screw around with sideloading updates to mobile? > it should be pretty straightforward, but i haven't messed with it, yet. > one of our apps runs on single-app-mode ios devices. so, we could pay for > mdm to update it, or we could sideload the updates. ___ 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: polygrid formatted column width
lcqc report 24493 added https://quality.livecode.com/show_bug.cgi?id=24493 On Tue, Feb 20, 2024 at 6:07 PM Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > Can I just say that the Datagrid does have all these properties? What is > the big advantage that would make Polygrids a better choice? Is it because > they are Mobile friendly? Faster for large datasets? Easier to work with > (apparently not unless by easier one means less properties that you can > manipulate.)? > > Bob S > > > On Feb 20, 2024, at 1:49 PM, Paul Dupuis via use-livecode < > use-livecode@lists.runrev.com> wrote: > > You have the dataWidth of the polygrid for the formattedWidth of the > widget (to be wide enough to display all data), but what I think you want > is some equivalent of the fomattedWidth of each column. I don't believe any > such property exists in the polygrid. > > ___ > 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 > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." ___ 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: polygrid formatted column width
yes, the dg does have all of these properties. i'm replacing a dg with a pg. dg's work on mobile, too. the scrolling can sometimes be a little hairy and jerky, but it does work. until the pg, nearly every project we built for mobes had at least one dg in them. i'm doing this because this project is being used for large datasets, pulling data from an erp odbc datasource. On Tue, Feb 20, 2024 at 6:07 PM Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > Can I just say that the Datagrid does have all these properties? What is > the big advantage that would make Polygrids a better choice? Is it because > they are Mobile friendly? Faster for large datasets? Easier to work with > (apparently not unless by easier one means less properties that you can > manipulate.)? > > Bob S > > > On Feb 20, 2024, at 1:49 PM, Paul Dupuis via use-livecode < > use-livecode@lists.runrev.com> wrote: > > You have the dataWidth of the polygrid for the formattedWidth of the > widget (to be wide enough to display all data), but what I think you want > is some equivalent of the fomattedWidth of each column. I don't believe any > such property exists in the polygrid. > > ___ > 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 > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." ___ 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: PDF widget print quality
I'm not sure it is possible. Livecode's printing tends to be card based and at card resolution, typically 72 dpi. I recall seeing some efforts on the lists and forums to make an object 4 times bigger (75 dpi x 4 = 300 dpi) so that when it is printed to a 300dpi printer is is a higher resolution but normal size but I don't recall how successful any of those efforts were. There is probably an ancient enhancement request in the Livecode Quality Center to support higher-resolution printing. On 2/20/2024 8:56 PM, David Epstein via use-livecode wrote: I want to use the PDF widget to print a PDF with additional markings added in LiveCode. Showing a simple PDF tax form in Widget 1 at 100% scale, I tried this script: on p1 get the pageRect of widget 1 open printing with dialog print card from (item 1 to 2 of it) to (item 3 to 4 of it) into it close printing end p1 This prints a full page at the proper size, but not with acceptable print quality; everything is slightly blurred and pixellated. How can I get a good quality printout? David Epstein ___ 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
