This topic contains 2 replies, has 2 voices, and was last updated by 
Sledge 1 year, 5 months ago.
-
Posts
-
This may be a long term thing but I only just noticed with the latest release (v1.1.08) under High Sierra: When launching from within Ted2, if you Print enough during execution your program will end up running in fits and starts. The less you log per frame the longer it takes, but it always seems to kick once you’ve logged a certain amount. (I habitually have every major method log that it was called at least, so even low-complexity stuff stutters after a short amount of time). Running the built product on its own results in normal behaviour, it’s just when you run from Ted2 and continually Print stuff — the CPU usage of Ted2 in Activity Monitor eventually goes over(!) 100% and it becomes unresponsive.
Yes, this issue has been in there for ages and I should probably get round to doing something about it one of these days, just not quite sure what exactly!
If Ted2 were to write the log stuff to a file and just tail out x lines during execution, that wouldn’t be the worst thing in the world. It could even present the whole file once execution halted so you could inspect it within the IDE after the fact. That pretty much covers normal usage, I think, where you’re really only interested in the last few log entries while the code is running, then want a more comprehensive view afterwards.
You must be logged in to reply to this topic.