A key to increasing the speed of game creation is to create custom editors for commonly used components. For the sake of example, we’ll use this very simple script that always keeps an object looking at a point.
//JS Example
var lookAtPoint = Vector3.zero;
function Update ()
{
transform.LookAt (lookAtPoint);
}
//C# Example
public class LookAtPoint : MonoBehaviour {
Vector3 lookAtPoint = Vector3.zero;
void Update ()
{
transform.LookAt (lookAtPoint);
}
}
//C# Example
public class LookAtPoint : MonoBehaviour {
Vector3 lookAtPoint = Vector3.zero;
void Update ()
{
transform.LookAt (lookAtPoint);
}
}
This will keep an object oriented towards a world-space point. Let’s make it cool!
The first step to making it work nicely in the editor is to make the script run even when you’re not testing the game. We do this by adding an ExecuteInEditMode attribute to it:
@script ExecuteInEditMode()
var lookAtPoint = Vector3.zero;
function Update () {
transform.LookAt (lookAtPoint);
}
//C# Example
[ExecuteInEditMode]
public class LookAtPoint : MonoBehaviour {
Vector3 lookAtPoint = Vector3.zero;
void Update () {
transform.LookAt (lookAtPoint);
}
}
//C# Example
[ExecuteInEditMode]
public class LookAtPoint : MonoBehaviour {
Vector3 lookAtPoint = Vector3.zero;
void Update () {
transform.LookAt (lookAtPoint);
}
}
Try adding the script to your main camera and drag it around in the Scene view.
This is all well and good, but we can make the editor for it a lot nicer by customizing it. To do that we need to create an Editor for it. Create a JavaScript called LookAtPointEditor in a folder called Editor.
@CustomEditor (LookAtPoint)
class LookAtPointEditor extends Editor {
function OnInspectorGUI () {
target.lookAtPoint = EditorGUILayout.Vector3Field ("Look At Point", target.lookAtPoint);
if (GUI.changed)
EditorUtility.SetDirty (target);
}
}
This class has to derive from Editor. The @CustomEditor attribute informs Unity which component it should act as an editor for.
The code in OnInspectorGUI is executed whenever Unity displays the editor in the Inspector. You can put any GUI code in here - it works just like OnGUI does for games, but is run inside the Inspector. Editor defines the target property that you can use to access the object being inspected.
The EditorUtility.SetDirty code is executed if the user has changed any of the values by checking GUI.changed.
In this case, we make one of the Vector3 fields like is used in the Transform Editor - like so:
There’s a lot more that can be done here, but this will do for now - We’ve got bigger fish to fry…
You can add extra code to the Scene View by implementing an OnSceneGUI in your custom editor. In this case, we’ll add a second set of position handles, letting users drag the look-at point around in the Scene view.
@CustomEditor (LookAtPoint)
class LookAtPointEditor extends Editor {
function OnInspectorGUI () {
target.lookAtPoint = EditorGUILayout.Vector3Field ("Look At Point", target.lookAtPoint);
if (GUI.changed)
EditorUtility.SetDirty (target);
}
function OnSceneGUI () {
target.lookAtPoint = Handles.PositionHandle (target.lookAtPoint, Quaternion.identity);
if (GUI.changed)
EditorUtility.SetDirty (target);
}
}
OnSceneGUI works just like OnInspectorGUI - except it gets run in the scene view. To help you make your editing interface, you can use the functions defined in Handles class. All functions in there are designed for working in 3D Scene views.
If you want to put 2D GUI objects (GUI, EditorGUI and friends), you need to wrap them in calls to Handles.BeginGUI() and Handles.EndGUI().
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More information
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising. Some 3rd party video providers do not allow video views without targeting cookies. If you are experiencing difficulty viewing a video, you will need to set your cookie preferences for targeting to yes if you wish to view videos from these providers. Unity does not control this.
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.