Puzzled by delayed action effect on changes to appended script...?
Unity Online Beginner Tutorial: Creating a Main Menu
I watched this tutorial, then grabbed a prefab menu from the Asset Store and tried installing it as Scene 0 in my n00bie student project. I have mostly succeeded -- I can switch to scene 1 (FPS 3d world) with a button click, and I can switch back to scene 0 (menu) using ESC in the game. Everything is fine except for one very frustrating gap in my knowledge: for an hour or more I struggled to get a visible cursor in the menu screen. I tried adding Cursor.visible = true to my breakout function (on ESC), etc. Nothing seemed to have any effect. I was really at my wits' end, until eventually (I have no idea why) I entered Play mode one more time and suddenly the cursor was visible -- apparently without my having changed anything between the "no cursor" and "cursor OK" states.
This could be simple n00by confusion, and I understand a reader's skepticism... but I'm pretty sure that I didn't change anything between "it doesn't work" and "it works."
Is this possible? Can anyone give me a clue? is there some latency between editing scripts in Mono Develop and their taking effect in the Unity working file? Something about OSX Unity interacting with El Cap's screen manager? I must have inadvertently refreshed something, but no idea what.
as long as you don't save the edited scripts, unity won't recompile them (happens to me once in a while)
Your answer