console disappears? 2020.3575

Solar2D General Questions/Discussion
#1

Hi,

I noticed that with 2020.3575 today, there was no Console Simulator Window … and attempts to get it to display by going to the main Corona task bar, ‘Windows’, ‘Console’ had no effect.  (The actual simulator displayed and ran ok.)

Oddly, the last released Corona (2018?) doesn’t have this problem.

It may be caused by a lack of internet connectivity … I have AT&T fiber, and it went down yesterday (and is still down).  To test that theory, I obtained a wifi hotspot, connected to it, started 2020.3575, and now I see a Console Simulator Window.  If this is true, it’s annoying: one shouldn’t need internet to debug (use the console).

So, might this be a relatively new bug (since the older Corona had no problem)?

As a separate problem, which I haven’t researched, I noticed that in neither the released Corona nor 

in 2020.3575 will clicking on the Console Simulator Window bring total focus to Corona (i.e., the Mac’s

top menu bar remains what it had been (e.g., Chrome, or Terminal, or whatever)). 

Clicking on the simulator window does, correctly, change the top menu bar to be “Corona Simulator”.

Perhaps the simulator console is some kind of second class window?

(MacPro laptop, running Mojave)

#2

Not quite as simple as having/not-having internet.  I killed the net, and Corona, and restarted 2020.3575: no console.

I restarted the net (wifi via hotspot), restarted Corona 2020.3575 and … no console.

I started released version (2018) and got a console.

#3

I have been running 3575 on a mac for about 2 weeks now and never had this problem. The console is always there.

#4

@sieler2 If this is what I think it is, you have to restart Corona and then it will work fine.   The mac console disappears - especially if you are running a bunch of print statements in a runtime loop.  The only way to get it back is to restart Corona.

It only takes a few seconds to restart so it’s pain I can live with for now.  Since the crashing is inconsistent I had misattributed it to several things it wasn’t related to but I’ve found other mac users encounter this occasional “restart” bug as well.

#5

@sporkfin although I thought I’d tried doing restarts, I can’t swear to it. 

I’ll do that next time, thanks.

And, your ‘print’ comment strikes home…I was doing a lot of prints trying to find a problem.

Stan

#6

It took several of us a while to figure that one out.  The hardest part is that it in inconsistent so hard to pin it on the correct source.

#7

Not quite as simple as having/not-having internet.  I killed the net, and Corona, and restarted 2020.3575: no console.

I restarted the net (wifi via hotspot), restarted Corona 2020.3575 and … no console.

I started released version (2018) and got a console.

#8

I have been running 3575 on a mac for about 2 weeks now and never had this problem. The console is always there.

#9

@sieler2 If this is what I think it is, you have to restart Corona and then it will work fine.   The mac console disappears - especially if you are running a bunch of print statements in a runtime loop.  The only way to get it back is to restart Corona.

It only takes a few seconds to restart so it’s pain I can live with for now.  Since the crashing is inconsistent I had misattributed it to several things it wasn’t related to but I’ve found other mac users encounter this occasional “restart” bug as well.

#10

@sporkfin although I thought I’d tried doing restarts, I can’t swear to it. 

I’ll do that next time, thanks.

And, your ‘print’ comment strikes home…I was doing a lot of prints trying to find a problem.

Stan

#11

It took several of us a while to figure that one out.  The hardest part is that it in inconsistent so hard to pin it on the correct source.