Doesn't KSP.IO support Binary Data?

[Fel]

Just questioning conventions; but if KSP.IO can be used to read Binary Data, what is the point of using UnityEngine.WWW?

http://docs.unity3d.com/Documentation/ScriptReference/Texture2D.LoadImage.html

I mean, they even have an interface for it!

And yeah... Byte[] KSP.IO.File.ReadAllBytes(String filename, Vessel flight)

Edited June 15, 2013 by Fel

[Fel]

Other than having to parse in as WWW, then output into the correct format (which can be done before packaging)

WWW img = new WWW(string.Format("file://{0}/HrmHaystack/images/{1}", KSPUtil.ApplicationRootPath.Replace("\\", "/"), filename));
Texture2D temp = new Texture2D(32, 32, TextureFormat.ARGB32, false);
img.LoadImageIntoTexture(temp);
KSP.IO.File.WriteAllBytes<HSBehaviour>(temp.EncodeToPNG(), filename, null);

I encounter no issues with doing

targ.LoadImage(KSP.IO.File.ReadAllBytes<HSBehaviour>(filename, null));

*Using haystack because I am lazy and wanted a simple example to test on

[Razchek]

By all means, use KSP.IO when possible. It will be more efficient than using the WWW class for larger files.

[jheriko]

surely using WWW is just bad practice? the potential overhead and security implications etc... best just to avoid altogether.

[EndlessWaves]

surely using WWW is just bad practice? the potential overhead and security implications etc... best just to avoid altogether.

KSP.IO is restricted to the PluginData directory so while it's great for storing and loading your own stuff if you want to share data between plugins or something else that requires access to a different part of the KSP directory it's of no use.

It should definitely be the primary choice though.