Should have seen this coming - Where to write temp files?

Chris Fullmer

Yeah, I'm writing a LOT of files and they are persistant while the model is open. So I could have a few thousand files xluttering up someone's desktop hehhe. Might not go over well.

I still can't figure out why my Mac tester's computer won't let me write to his temp folder. It lets me create my folder, but then won't let me write to it.....grr. Oh yes, though come to think of it, he has not tested my new version using the different permission settings the Jim and Dan suggested. I better get him to try that soon.

Dan Rathbun

And you may have set the "special" bits, by accident, when you sent int(777) instead of int(511)...

.. I suggest having the tester, totally delete the folder manually, before trying the new version.

Chris Fullmer

Ahh, good point.

Thanks so much everyone for all the help always. Its nice to be able to help people from time to and time, and even nicer when there are amazing people out there who are willing and able to help when needed. Very grateful, thanks Dan (et al)

Chris

Dan Rathbun

Just noticed ANOTHER standard Ruby extension that bears on this subject.

With a path to the local standard Ruby lib dir pushed into the $LOAD_PATH array, you add the following to your module:
require('tmpdir.rb')

This standard extension adds the class methods:
Dir::tmpdir and Dir::mktmpdir

If you read the file, you'll recognize the Dir::tmpdir method as the 'progenitor' of the edition in the Google 'webtextures_loader.rb' file. (Google "lifted" it, and stripped out the Win32 specific part.)

So (above) when we talked about whether to rely on the WebTextures plugin, my advice is, to instead rely on the Standard Ruby library.