Re: Anyone else experience this bug?

Thanks for that info Curry, there is more than one of them for sure. I sometimes get it when exiting group editing, but that one is rare. On Thu, Jan 5, 2023 at 1:21 AM Curry Kenworthy via use-livecode < use-livecode@lists.runrev.com> wrote: > > > livecode process just goes poof > > Has any

Re: Anyone else experience this bug?

> livecode process just goes poof > Has anyone else experienced it? Me! I get the IDE Vanishing Act on Windows, once per week. But perhaps a DIFFERENT bug or a different trigger: Not when interacting specifically with Styled text. Best wishes, Curry Kenworthy WordLib: Import MS Word an

Re: Anyone else experience this bug?

Thank you all for your responses. Knowing that it has to do with Styled text is a big help, thanks Mark W. Bob, the crash report is in the bug report. Mathias, unfortunately I cannot post a sample stack. I cannot reliably reproduce it myself. The fields in the one code base,Appli, are heavily styl

Re: Anyone else experience this bug?

On 1/3/23 20:22, Tom Glod via use-livecode wrote: Hi Folks, I work with 2 completely different codebases every week. On both I and (we) experience hard crashes to desktop, where livecode process just goes poof Usually it is triggered by either a mouseUp or mouseDown ... most likely UP. The bug i

Re: Anyone else experience this bug?

Tom, does this happen with every stack that contains such a "special" field or only with one stack? What field type is it? Scrolling field, Scrolling list field or table field? I created a stack here with a Scrolling list field, added some lines of text and changed the backgroundcolor of some li

Re: Anyone else experience this bug?

Seems there ought to be a crash log somewhere that could give clues. On the Mac you can open the Console app, click the Crash Reports in the left pane, and search for Livecode. But I am not exactly sure that the crash logs will indicate application crashes. Bob S On Jan 4, 2023, at 08:22 , To

Re: Anyone else experience this bug?

Sean, not that I know of. I am the only common denominator right now. I would be happy to find out its me if only it meant that this issue be solved. I hear you Craig, I hear you. On Wed, Jan 4, 2023 at 8:11 AM Craig Newman via use-livecode < use-livecode@lists.runrev.com> wrote: > I have been

Re: Anyone else experience this bug?

Not that it helps, but I haven't had CTDs in a long time. I will note however that one of the causes of past CTDs is an endless loop. If the engine gets so many loops in a short period of time, it's my understanding it will CTD. If it's a click anywhere in the app, I would look at any front or b

Re: Anyone else experience this bug?

I have been plagued by arbitrary crashes forever. Probably a few times per month. But since I cannot post a repeatable example, I have nothing but sympathy from the forum members. Note though that those members generally do NOT see this issue at all. Craig > On Jan 4, 2023, at 5:20 AM, Sean Co

Re: Anyone else experience this bug?

I am not noticing this using LC quite extensively over the holidays. Is there any code or library common to both codesets that utilises mouseUp messages in the stack or card script? This would be my first place to look. Sean Cole *Pi Digital Productions Ltd* eMail Ts & Cs

Anyone else experience this bug?

Hi Folks, I work with 2 completely different codebases every week. On both I and (we) experience hard crashes to desktop, where livecode process just goes poof Usually it is triggered by either a mouseUp or mouseDown ... most likely UP. The bug is not consistent and does not happen when clicking a