On 8/12/19 7:29 PM, Richard Gaskin via use-livecode wrote:
Mark Wieder wrote:
> A stack's breakpoints are stored in the cREVGeneral["breakpoints"] of
> the stack itself...
When did this happen? IIRC for most of MC/LC's life the breakpoints
were an engine-level stack property.
"the
Mark Wieder wrote:
> A stack's breakpoints are stored in the cREVGeneral["breakpoints"] of
> the stack itself...
When did this happen? IIRC for most of MC/LC's life the breakpoints
were an engine-level stack property.
--
Richard Gaskin
Fourth World Systems
Software Design and Development
On 8/12/19 10:41 AM, J. Landman Gay via use-livecode wrote:
On 8/12/19 8:32 AM, Sannyasin Brahmanathaswami via use-livecode wrote:
Switching to hard coded "breakpoint"
It a tricking thing "clearing" those
I sometimes use Matthias' method but since the crash report I've started
marking my
On 8/12/19 1:19 PM, Martin Koob via use-livecode wrote:
Sometimes it works beautifully at each breakpoint the script stops. other times
it doesn’t stop at all or stops only at open scripts. Also I have the problems
of not being able to always delete the red dots. In a bit more detail here is
There was a post earlier where someone mentioned that Panos is onto this one
and is looking into it.
Bob S
> On Aug 12, 2019, at 13:19 , Martin Koob via use-livecode
> wrote:
>
> I just got used to the flakiness of the red dot breakpoints so adapted my
> workflow with workarounds to use
I just got used to the flakiness of the red dot breakpoints so adapted my
workflow with workarounds to use them.
When I am debugging I want to follow through different objects that the script
jumps to. I have the red breakpoints in the different objects, i.e. Button ->
group-> card->
On 8/12/19 8:32 AM, Sannyasin Brahmanathaswami via use-livecode wrote:
Switching to hard coded "breakpoint"
It a tricking thing "clearing" those
I sometimes use Matthias' method but since the crash report I've started
marking my breakpoints with a special comment like this:
Hi Hermann,
> Am 10.08.2019 um 19:32 schrieb hh via use-livecode
> :
>
>> Klaus M. wrote:
>> yes, success, at least partly, now I get a SHELL error -> ... access denied
>> Although I "chmod"ded that file to "777" (via the INFO window on my Mac), so
>> everyone should be able to access it,
My stack is a (simple) QR Code *reader* not a *scanner*.
It reads from static images.
That is, if you use a webcam on desktop or a built-in camera on mobile you have
to take a (sharp) picture and then select from that picture to read the code.
Usually a webcam or a mobile that cannot do an
I wouldn't Google, "Sacrificing Chickens" these days. You might get a visit
from some unpleasant people. ;-)
Bob S
> On Aug 10, 2019, at 22:49 , scott--- via use-livecode
> wrote:
>
> Hello Alan,
>
> I only said that it works for me… I have NO idea HOW it works :- )
> If it were me I would
Jacque has a handy tool called Airlaunch that allows you to deliver
builds over the air (via web server).
[https://livecode.com/products/thirdparty/hyperactivesw/airlaunch-1-0-0/]
Another option is to save the standalone and install directly via the
Devices panel in Xcode.
> Switching to hard coded "breakpoint"
> It a tricking thing "clearing" those
Currently i am doing it this way.
At the first line of a script i have "put TRUE into tDebug"
and my breakpoints are set this way.
"if tDebug then breakpoint"
If i don´t want them to be active anymore i
I'm curious (as i'm working with it also), if you are able to turn it
off and on.
1. The barcode widget seem not to react to:
set the disabled of widget"Android Barcode Scanner" to true (or false)
or either
set the enabled of widget"Android Barcode Scanner" to true (or false)
The
I've been debugging code and "fell" into old habit of using "red dot
breakpoints"
-- crashing every 10 minutes! No recipe...
I guess I don't need to report this, but just saying "it a real pain"
Switching to hard coded "breakpoint"
It a tricking thing "clearing" those
BR
J. Landman Gay
14 matches
Mail list logo
