Type mismatch in Demo05_Sets about unite2017 HOT 4 CLOSED

It is safe...

This is just an editor display issue, the data is in tact. What is happening is the inspector is assuming that it is resolving an asset reference rather than a scene object reference.

It is simple enough to make a custom editor for the inspector or to use a property drawer to get your display back for debugging. If you do not want to edit the data in the inspector, you can simply draw EditorGUI.ObjectField with allowSceneObjects true. If you do want it to be editable in the inspector it can get more complicated to do it genericly.

from unite2017.

I think this is due to the Scriptable object trying to reference a Gameobject, which would result in a type mismatch. I believe that the way Ryan implements this is a very clever way enable a reference to the gameobject.

For example in his ThingDisabler Script (which is a Monobehaviour) he can do this:

Set.Items[i].gameObject.SetActive(false);

which allows his to reference the "Set" and find gameobjects then delete them.

Really clever, not sure if I'm answering this correctly however.

from unite2017.

Some more proof to the previous answer.
If we change RuntimeSet to:

public abstract class RuntimeSet<T> : ScriptableObject
{
	public List<string> gameobjectNames = new List<string>();
	public List<T> Items = new List<T>();

	public void Add(T thing, string name)
	{
		if (!Items.Contains(thing))
			Items.Add(thing);
			gameobjectNames.Add(name);
	}

	public void Remove(T thing, string name)
	{
		if (Items.Contains(thing))
			Items.Remove(thing);
			gameobjectNames.Remove(name);

	}
}

and change Thing.cs to:

public class Thing : MonoBehaviour
{
	public ThingRuntimeSet RuntimeSet;

	private void OnEnable()
	{
		RuntimeSet.Add(this, this.name);
	}

	private void OnDisable()
	{
		RuntimeSet.Remove(this, this.name);
	}
}

we can see this is actually working.

from unite2017.

Yeah, i know it's working.
Assets can reference scene objects until new scene is loaded.

My question was: Can i ignore that "Type mismatch" labels and be sure nothing will suddenly break

from unite2017.