Re: Is there a way to manually trigger GC?

Hi Tom, Does hasMemory() have any effect on available memory, or does it truly just report the state of things? I wonder if there is some shell command that might help? Phil Davis On 1/16/21 11:31 AM, Tom Glod via use-livecode wrote: Hi Folks, I'm finding my application does a nice job

Is there a way to manually trigger GC?

Hi Folks, I'm finding my application does a nice job to unload data from memory, but it takes a while for that to happen. When the initial load of the application occurs, the memory consumption is quite high if there is lots of data to be loaded (1 GB+). But after a while, the used ram drops

Printing borked for LC Linux?

I've been printing almost exclusively to PDF for the last several years, but this morning I wanted to print to actual paper, and found that LC doesn't print from Ubuntu. There's nothing in the result after the print command, so LC thinks it's doing fine. And I can print from any other app

Re: opened socket in IDE prevents script changes

Look in the script editor breakpoints tab. If there are any there delete them. Just spitballing. Bob S On Jan 16, 2021, at 7:10 AM, Bernard Devlin via use-livecode mailto:use-livecode@lists.runrev.com>> wrote: Hi Bernd Thanks for the suggestion. But I think the evidence points away from

Re: mobileControlCreate (set, do, etc)

Another idea is to place a graphic where you want the object to be in the IDE so that you can “see” it and then use the rect of the grc to set the rect of the mobile control. I will echo building a smaller test stack. My mobileDemo stack doesn’t take anywhere near that long to build. Sent

Re: opened socket in IDE prevents script changes

Hi Bernd Thanks for the suggestion. But I think the evidence points away from this. One thing I've done is - change the script (could be just addition of a comment) - copy entire script - apply & close - re-open script editor --> *change is missing* - close IDE - re-open LC - open stack script

Re: mobileControlCreate (set, do, etc)

Hi Sannyasin, Two suggestions. Could you build a small test stack to test your idea and refine it? Not sure of your hardware, but that might be faster to load than a larger, more complicated application. Also, the simulator might be another possible option to speed things up while testing?