On 09/09/16 08:54, Graeme Geldenhuys wrote:
On 2016-09-08 19:07, Martin Frb wrote:> And you need to press the "current" button in the stack. doubleclick > does not select it. Ah, that was the problem. Thanks for help. Amazing I never noticed itbefore.
Thanks also from me, I'd always assumed there were good reasons for that behaviour (stack destroyed by exception or somesuch) which I think makes Graeme's question pertinent:
A question though:Why must you click "current" before the stack (an local variables)update? Wouldn't that be the obvious thing to do (desired behaviour)when you double click back into the stack history? The "current" buttonjust seems redundant. Regards, Graeme
-- Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues] -- _______________________________________________ Lazarus mailing list [email protected] http://lists.lazarus-ide.org/listinfo/lazarus
