Re: Diagnosing a crasher (was Re: Quality, reputation, and improving both)

Not to cast aspersions on anyone's work, but there is an alternate script editor that misbehaved in a similar way when switching between the native editor and the alternate one. That has been ironed out some time ago, but for the sake of historical accuracy... well... there you go. Bob S > O

Re: Diagnosing a crasher (was Re: Quality, reputation, and improving both)

dunbarx wrote: > All. > It did just occur to me that ALL my crashes occur when the SE is open. > Never just playing with the stack. I am trying to remember now whether > I am modifying code or not when the crash occurs. The problem, > (actually the beauty, of course) of LiveCode is that one can ju

Re: Diagnosing a crasher (was Re: Quality, reputation, and improving both)

All. It did just occur to me that ALL my crashes occur when the SE is open. Never just playing with the stack. I am trying to remember now whether I am modifying code or not when the crash occurs. The problem, (actually the beauty, of course) of LiveCode is that one can jump in a and out of the

Re: Translate metadata to field content

On 2/21/20 2:10 PM, J. Landman Gay via use-livecode wrote: The only reason I have more than one instance is because there are href links inside the metadata spans, and LC translates that into separate metadata spans if there is more than one link, or there's a line break. If it would honor the e

Re: Diagnosing a crasher (was Re: Quality, reputation, and improving both)

On 2/21/20 2:44 AM, Richard Gaskin via use-livecode wrote: J. Landman Gay jacque wrote: > We're about to submit the iOS app now and my testers have had several > intermittent crashes we can't repeat, even though I built that one > with 9.5.1 stable. I submitted crash logs but the team could on

Re: Diagnosing a crasher (was Re: Quality, reputation, and improving both)

Curry. We are all fortunate in that you found the culprit in a single command in a line of code. It crashes LC 9.5.1 in Mac OS. If I change the second parameter (tDel) to a single char, all is well, The issues I am having with my project occur in random places in different handlers at random tim

RE: Diagnosing a crasher (was Re: Quality, reputation, and improving both)

I have an IDE bug that I have to get a recipe for. It might not be possible to whittle this one down and I might have to send Panos the full stack with data files off line. 1) After the openCard message is passed to the engine if the script editor is open the engine loops for 5-10 seconds before t

Re: Translate metadata to field content

On 2/21/20 2:51 AM, Mark Waddingham via use-livecode wrote: Both characters and codepoints run the risk of requiring a linear scan of the string to calculate the length - strictly speaking his will occur if the engine is not sure whether character / codepoint have a 1-1 map to codeunits (for exam

Re: Translate metadata to field content

Welcome to the party Hermann. :) Unfortunately the HTML isn't under my control and may change periodically. It's retrieved from a server on demand. The metadata I'm looking for isn't a link, it's a text property, and is already hidden when displaying text in a field. It would be similar to looki

Re: Translate metadata to field content

Mark Waddingham wrote: > On 2020-02-21 17:22, Richard Gaskin via use-livecode wrote: >> This is an interesting detail. Is it safe to surmise from this that >> in cases where speed is important we should consider using codeunits >> instead of chars? > > Yes - especially if searching for non-lette

Script editor inserting periods

For some reason LC is auto inserting periods in the script editor - at the end of what it thinks is a sentence. If I don’t catch it then the code breaks of course. Is there somewhere I can turn that off? Couldn’t see anything in preferences. (LC 9.5.1) Marty

Re: Translate metadata to field content

Yes, any additions are good to have. I hope someone updates it. JB > On Feb 21, 2020, at 10:41 AM, Bob Sneidar via use-livecode > wrote: > > Yes, that's it, but not sure if some of these recent gems are getting into > the library. > > Bob S > > >> On Feb 21, 2020, at 10:22 , JB via use-li

Re: Diagnosing a crasher (was Re: Quality, reputation, and improving both)

Chiming in again since it dovetails with today's work: Crashing bugs (and others) sometimes require a missing factor/context/detail in the original real-world project that is tricky to reproduce in independent test stacks. You have to compensate for that. I filed this crasher today, but had

Re: Translate metadata to field content

Yes, that's it, but not sure if some of these recent gems are getting into the library. Bob S > On Feb 21, 2020, at 10:22 , JB via use-livecode > wrote: > > I thought Michael Doub was handling the Master Library or > are you talking about something else? > > JB __

Re: Translate metadata to field content

I thought Michael Doub was handling the Master Library or are you talking about something else? JB > On Feb 21, 2020, at 7:50 AM, Bob Sneidar via use-livecode > wrote: > > Is anyone maintaining the MasterLibrary? Stuff like this really should be > added to it when the kinks are worked out. >

Re: Translate metadata to field content

Aha! Of course. I should have thought of that. Mark pointed out the same thing. (And yes, my brief test had the metadata in the third paragraph.) I'll try his handler when I get back to my Mac. If my guess is correct, the search won't take any measurable time at all and the primary delay will b

Re: Translate metadata to field content

On 2020-02-21 17:22, Richard Gaskin via use-livecode wrote: This is an interesting detail. Is it safe to surmise from this that in cases where speed is important we should consider using codeunits instead of chars? Yes - especially if searching for non-letter chars as delimiters (e.g. return,

Re: Translate metadata to field content

Mark Waddingham wrote: >> I'm using chars instead of codepoints because when I tried it, they >> both gave the same number. Should I change that? > > Both characters and codepoints run the risk of requiring a linear scan > of the string to calculate the length - strictly speaking his will > occur

Re: Translate metadata to field content

Is anyone maintaining the MasterLibrary? Stuff like this really should be added to it when the kinks are worked out. Bob S > On Feb 21, 2020, at 24:51 , Mark Waddingham via use-livecode > wrote: > > On 2020-02-21 00:29, J. Landman Gay via use-livecode wrote: >> So glad you chimed in, Mark.

Browser Widget different actions on Mac/ios and Windows

I posted this on the forum ://forums.livecode.com/viewtopic.php?f=8&t=33705 Lagi ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe an

Re: Translate metadata to field content

Hi Jacque, Jacque wrote: > put the styledText of fld 1 into tDataA > put 0 into tTotalChars > put 0 into tStartChar >repeat with i = 1 to the number of elements in tDataA >put tDataA[i]["runs"] into tRunsA >repeat with j = 1 to the number of elements in tRunsA > put tRunsA[j] in

Re: Translate metadata to field content

On 2020-02-21 00:29, J. Landman Gay via use-livecode wrote: So glad you chimed in, Mark. This is pretty impressive. I'll need to use the "for each element" structure because my tags are not unique, but it still is much faster. When clicking a tag at the top of the document that links to the last

Re: Diagnosing a crasher (was Re: Quality, reputation, and improving both)

J. Landman Gay jacque wrote: > We're about to submit the iOS app now and my testers have had several > intermittent crashes we can't repeat, even though I built that one > with 9.5.1 stable. I submitted crash logs but the team could only > repeat the problem once and there's no real recipe. How >