Re: Windows Standalone Performance

Hi Neville From my stance I have never seen this behaviour for any version of LC from any stack ide or standalone on Mac, Windows XP/7/8/10 native or via ParallelsDesktop. Perhaps you could do a few screen recordings using an external device like your phone and show the task manager reporting d

AW: Re: OT: HTML img src and Windows problem

On 12/11/2019 6:38 PM, Paul Dupuis via use-livecode wrote: This is not directly related to LiveCode. I amwriting a bunch of html from LiveCode to a local .html file. In it there are image tags to images in the same location as the .html file, so an image tag in the HTML might be: Not matter

Re: Windows Standalone Performance

This bug was reported some time ago https://quality.livecode.com/show_bug.cgi?id=21305 Saving a 9 megabyte stack in Windows 10 can take 10 seconds or more. It is not caused by Windows Defender or anti-virus software. _

Re: OT: HTML img src and Windows problem

This is all OK assuming your html file is in /Users/paul/Desktop/help/. It works here with all modern browsers. The error is caused somewhere else in your webpage. Contains the char-attribute a gremlin or did you set a conflicting base url? You could use the WebInspector of the browser to see w

OT: HTML img src and Windows problem

This is not directly related to LiveCode. I amwriting a bunch of html from LiveCode to a local .html file. In it there are image tags to images in the same location as the .html file, so an image tag in the HTML might be: Not matter what browser I open the HTML file in under Windows 10 (Fir

Re: Animated Gifs - Keep them Running

I read and agree. I think certain tasks ought to have independent threads separate from the code engine. That shouldn't be too hard to implement, and those tasks would not need to communicate with the main thread, since they are essentially utilitarian in nature. Bob S > On Dec 10, 2019, at

Re: Windows Standalone Performance

I like that. Looking on the bright side. :-) And of course you are right, saving multiple times is not a good thing, but I did this back when we had that bug where saving scripts actually didn't for whatever reason, and I had some crash to desktop issues as well, prompting me to insert an auto s

Re: Windows Standalone Performance

> No one is going to turn off their file AV LOL - yes, but that would be entirely your idea, not mine. As I said, yet another reason to code with care. Saving a stack multiple times while launching is not a good habit. Bad habits add up to hurt Mac apps too. The AV did you a favor with exa

Re: Groups in the message path: Trapping Mouseup

On 12/10/19 9:20 PM, Richard Gaskin via use-livecode wrote: The Message Path discussion starts on p 101, with a pretty good diagram on p 102, including a distinction between Groups and Backgrounds. OMG - there's documentation? Admittedly I haven't looked at the User Guide in quite a while. T

Re: Groups in the message path: Trapping Mouseup

The PDF files are generated from .md files. The guides are split between two locations: https://github.com/livecode/livecode/tree/develop/docs/guides https://github.com/livecode/livecode-ide/tree/develop/Documentation/guides Thanks, Brian On Wed, Dec 11, 2019 at 12:21 AM Richard Gaskin via use-l

Re: Groups in the message path: Trapping Mouseup

Richard, I'm not sure you were posting this to the right forum. You see, this is the Livecode forum. We don't need no stinking User Guides! :-) Bob S > On Dec 10, 2019, at 21:20 , Richard Gaskin via use-livecode > wrote: > > Paul Dupuis wrote: > > Richard Gaskin, at one point, had a really e

Re: Windows Standalone Performance

Easy enough to test. I'll do that later and get back with results. It's definitely worth exploring, but I can short cut that a bit by saying that since virtually everyone with any sense has some kind of protection, even if it's Windows Defender, but also other protection on top of that, the exer

Re: Windows Standalone Performance

Bob Sneidar wrote: > Just wanted to give a heads up on what I think is the greatest Windows > Standalone performance killer. .. > On a Mac, for whatever reason, the performance hit was insignificant. > On WINDOWS however, it became painfully clear to me that the > performance penalty was VERY sub