Craig:
> I never minimize the SE, if that is the required
> starting point of the bug.
Given a recipe, that's not a conclusion we can draw;
all we know is that this recipe triggers the bug.
Could a variation also trigger the bug? Maybe; try it.
The point is: here I successfully recipe'd a bug
Curry.
I never minimize the SE, if that is the required starting point of the bug.
Craig
> On Oct 29, 2021, at 10:48 PM, Curry Kenworthy via use-livecode
> wrote:
>
>
> Craig:
>
> > The project will run fine for months, in constant use,
> > but then crash. Not reproducible as far as I can
Craig:
> The project will run fine for months, in constant use,
> but then crash. Not reproducible as far as I can tell.
> Just crashed, Again, working in the IDE,
> SE open, fixing and enhancing.
Here's another bug that may "hint" at similar IDE behavior,
although it doesn't give me a cras
Oh that's right I knew about this! Do I keep asking the same questions over and
over? ;-|
Bob S
> On Oct 29, 2021, at 09:28 , Richard Gaskin via use-livecode
> wrote:
>
> Bob Sneidar wrote:
>
> > Has anyone written something that will trace the flow of a command
> > or procedure and create
Curry.
Just crashed, Again, working in the IDE, SE open, fixing and enhancing. Saved
fairly recently, so only a minor hassle.
Craig
> On Oct 29, 2021, at 12:28 PM, Richard Gaskin via use-livecode
> wrote:
>
> Bob Sneidar wrote:
>
> > Has anyone written something that will trace the flow of
Bob Sneidar wrote:
> Has anyone written something that will trace the flow of a command
> or procedure and create some kind of rudimentary flow diagram? It
> can be text based something like:
>
>stack "Main Form"
>Openstack
>setSubscriptions
>
Craig:
> The project will run fine for months, in constant use,
> but then crash. Not reproducible as far as I can tell.
Roger that, I'll keep an eye out.
If enough crashers get recipe'd generally,
maybe we'll be lucky and hit yours too!
Best wishes,
Curry Kenworthy
Custom Software Develop
Curry.
It always happens in the IDE when I am working on my largest desktop project,
an eight year old mainStack that contains six substacks. I work on that project
only on my main office computer. Invariably I am fooling around between the SE
and the mainStack.
It has never happened when I am
Craig:
> My one entry into the "bug” poll was to complain
> about random crashes of LC itself now and then.
> Not likely to have that solved anytime soon.
It could be! There is de-crashing LC progress, but it's slow.
This year I reported a crash/hang pair, and that's fixed now.
The problem is
Message Watcher? AHA.
My one entry into the "bug” pollI was to complain about random crashes of LC
itself now and then. Not likely to have that solved anytime soon. But I am
tempted to categorizes as a bug a sorely missing feature of the message watcher:
In the Forum
"https://forums.livecode.
Yes, but the message watcher is way too verbose. I do not need every system
message, only the ones called by my own code, and I need to at least be able to
discern when procedures exit.
My reason is that I have 15+ modules that all need to use the publish and
subscribe method I am implementin
Like LC's Message Watcher?
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On October 28, 2021 11:28:34 AM Bob Sneidar via use-livecode
wrote:
Has anyone written something that will trace the flow of a command or
procedure and create s
I suppose I could use the procedure that keeps track of the execution contexts
to create a logging method. Anyone know what and where that procedure is?
Bob S
> On Oct 28, 2021, at 09:26 , Bob Sneidar via use-livecode
> wrote:
>
> Has anyone written something that will trace the flow of a c
Has anyone written something that will trace the flow of a command or procedure
and create some kind of rudimentary flow diagram? It can be text based
something like:
stack "Main Form"
Openstack
setSubscriptions
s
14 matches
Mail list logo
