Probably should have broken this into two posts but don't want to clutter too much.
Short question...my SL directory is now jam packed full of .tmp files. I'm sure I can just delete them to no ill effect, just wondering if this is intentional for debug or something? They range in size from 1 to 384 KB so the total disk usage is not entirely trivial...and there's at least 40 of them or so. It's not causing me any problems, just curious.
Second question...I came by this while building my clock, which required some of the more precise use of the tools for me up to this point, then tried to duplicate the issue on a straighforward simple item and succeeded.
When I am editing an object, if I have focus on the object, then change a script in that object's content folder and recompile, I will have to lose focus on the object in order to mouse over and activate a "touch" event. However, if I leave the script open (while not focused), and change/recompile, I can just mouse over and see the event is available, which is great. I'm assuming this is intentional, but just checking...it makes sense (though it means that if you are working on a complex object, like a set of intertwined gears, and one of the harder-to-get-at ones requires a touch to activate, you have to lose focus, then work your way all the way into the gears using ALT focus, then touch). Voice activation or entry will get me around this sure, but sometimes it's good to see the event is available without having to actually kick it over.
Now, when I uncheck "running", then edit and recompile, then lose focus and mouse over, (or sans lose focus if I'm using the non-focus save/recompile) I don't get the "hand" to indicate that there is a touch event waiting for me until I actually move the object, even just hair. Once I move the object and lose focus, I get my touch hand. I'm thinking this is not intentional.
Izzitso?
I've been eyeballing the "Reset" button in the script window, but using it hasn't had any effect. I'm afraid I really don't know what that button does...does it ensure that the object is reset to react to the default state?