LiveCode Forums

I have a standalone (Mac OS X High Sierra, livecode 8.1.8 ) - let's call it "myApp" which opens a data stack "myData". In myData I call start using stack "myApp" and myApp certainly appears in the stacksinuse. All works fine in the development environment, but in the standalone *sometimes --- I thin...

Inserting an item into a line in a field where the line has fewer items has an unexpected (and incorrect) result. The bug has been confirmed by Quality Control in LC 7.x and 8.0 [ http://quality.livecode.com/show_bug.cgi?id=17590 ], while LC 6.7.x behaves correctly. Set up a field with contents a,b ...

Good one! Definitely a code snippet to squirrel away in a macro.

The LC team has noted the feature request, evidently not such a hard thing to implement, at least on MacWinLin.

Thank you.

I have formatForPrinting working, with some minor problems of measureText not giving quite accurate results and clear backgrounds being rendered in grey, both surmountable problems. Printing to PDF would be a much less cumbersome (and generic) solution however so I will be making a feature request f...

B***er! If LC produces PDF it ought to be able to print it. I was hoping to avoid formatforprinting, it just seems too weird - only works with an invisible stack which has to be closed purged and then re-opened, don't edit ... that surely must have been a temporary kludge for which I guessed "open p...

I have a card which prints correctly in MacOS using "print cd ..into.." but the formatting goes awry (in fact some bits don't print at all) in Windows. I gather the correct solution is to use "open printing for PDF". Great, it produces a correct PDF file on both platforms. Now how do I print the PDF...

Confirmed by Quality Control [bug 16947]. Still present in 8.0-DPx

Sadly -hh, in my testing all the leaks (or maybe *the* leak) are still there in 7.1.2-rc2 - on LC Launch, on drag and on my recursion (So why doesn't your code leak? only difference I can see is you lock screen and messages...)

My code wasn't crashing, just bleeding memory (my game does crash when the used memory gets into the gigabyte range of course). I admit I haven't tried 7.1.2-rc2 - maybe it's all fixed there - QC was working on fixing the first leak concerning drag, and it could be that fixed everything! Will do so ...

That's neat. I don't think I have ever used get!

I wouldn't be surprised if the leaks have nothing specifically to do with recursion, but are all instances of just one leak in the event handling code.

doRecurse() is a function so must return a value; doesn't compile without the return. But you do have a point - I wrote this example as a function because that what my actual code uses, using procedures and storing the final value somewhere rather than returning on the stack could conceivably make a...

OK I've set up a very simple stack calling a very simple function recursively to a depth of 400, and watch using the Xcode tool Leaks. It does indeed show a memory leak when the recursion finishes. But actually it shows a memory leak if you do any editing on the stack! Dragging the button I already ...

Many thanks Richard I have already submitted to QC the bug concerning a leak on LC launch [Confirmed bug 16943]. Concerning what I suspect is a bug on memory for function stacks not being released when the event loop is not being called often enough, the code I have is far too complex to offer for a...

I am writing a board game and need to use a deeply recursive algorithm to evaluate a position. Someday someone must explain the mysteries of recursion in LC: I tested a very simple recursive call to a function with just two integer parameters, which runs into the recursionLimit of 400000 after just ...

Confirmed [Bug 16893] present since LC6.7.x