Click through - Revision history

185.216.48.63: /* Use Input.Unhandled */

2017-10-02T18:18:40Z

‎Use Input.Unhandled

2017-04-19T05:06:14Z

2017-04-19T05:05:48Z

‎Setup an EventTarget MonoBehaviour

2017-04-15T07:52:15Z

‎Alternative design

2017-04-15T07:50:31Z

‎Alternative design

2017-04-15T07:43:28Z

‎Alternative design

2017-04-15T07:41:00Z

‎Alternative design

2017-04-15T07:36:54Z

‎Alternative design

2017-04-15T07:33:39Z

‎Alternative design

2017-04-15T07:32:12Z

‎Alternative design

@@ Line 38: / Line 38: @@
 </syntaxhighlight>
-PowerUI tries to give your input system as much flexibility as possible, so the above route is considered relatively low level and which allows you to pipe those events wherever you need them, but requires a little more scripting to hook it up.
+PowerUI tries to give your input system as much flexibility as possible, so the above route is considered relatively low level and which allows you to pipe those events wherever you need them, but requires a little more scripting to hook it up. PowerUI.Input.Unhandled is just an EventTarget instance which you can replace with a custom object too to e.g. divert everything.
 === Setup an EventTarget MonoBehaviour ===

← Older revision		Revision as of 05:06, 19 April 2017
Line 88:		Line 88:

	</syntaxhighlight>		</syntaxhighlight>
−
−	~~== Alternative design ==~~
−
−	~~PowerUI could use reflection like Unity does to look for OnMouseDown(MouseEvent e) and similar methods so your scripts could be like this instead:~~
−
−	~~<syntaxhighlight lang="csharp">~~
−	~~public class MyGameworldEvents : MonoBehaviour{~~
−
−	~~public void OnMouseDown(MouseEvent e){~~
−
−	~~// This runs when this gameobject got clicked on~~
−	~~// and the UI was not.~~
−	~~// Importantly, you have extra information about this particular click~~
−	~~// such as the finger that caused it.~~
−	}
−
−	}
−	~~</syntaxhighlight>~~
−
−	~~The bonus being it would easily work with all of your custom events too:~~
−
−	~~<syntaxhighlight lang="csharp">~~
−	~~public class MyGameworldEvents : MonoBehaviour{~~
−
−	~~public void OnMissionComplete(MissionEvent e){~~
−	~~// A mission was completed~~
−	~~// and the event was dispatched to this gameObject.~~
−	}
−
−	}
−	~~</syntaxhighlight>~~
−
−	Whenever an event is first dispatched to a gameObject, it would collect the handlers by looking for methods which accept 1 event object and start with 'On', then pass them to addEventListener. That should ultimately be only a small amount of extra overhead for lots more convenience - Any opinions?

@@ Line 42: / Line 42: @@
 === Setup an EventTarget MonoBehaviour ===
-This is the easier route, but involves PowerUI defining more of your input system. This also has the advantage of being able to correctly handle 3D [[Context Menu|context menu's]] too. Firstly, add something like the following to your project:
+This is the easier route, but involves PowerUI defining more of your input system. This also has the advantage of being able to correctly handle 3D [[Context Menu|context menu's]] too. Firstly, tick the "Handle 3D Input" box in '''Window > PowerUI > Input Settings''', then typically all you'll need to do is just add "MouseEvent" to e.g. OnMouseDown. Here's an example:
 <syntaxhighlight lang="csharp">
 public class MyGameworldEvents : MonoBehaviour{
-     public void Awake(){
+     public void OnMouseDown(MouseEvent e){
-         // Get the event target:
+         // To 'convert' a method, all we've really done is add the MouseEvent parameter.
-        var target = gameObject.getEventTarget();
+         // That makes it much better at dealing with multitouch too.
          // This runs when this gameobject got clicked on
          // and the UI was not.
@@ Line 160: / Line 71: @@
 // Dispatch it to a gameobject:
 aGameObject.dispatchEvent(e);
 </syntaxhighlight>

@@ Line 174: / Line 174: @@
          // This runs when this gameobject got clicked on
          // and the UI was not.
+         // Importantly, you have extra information about this particular click
+     }

@@ Line 170: / Line 170: @@
 public class MyGameworldEvents : MonoBehaviour{
      public void OnMouseDown(MouseEvent e){
@@ Line 186: / Line 185: @@
 public class MyGameworldEvents : MonoBehaviour{
      public void OnMissionComplete(MissionEvent e){
          // A mission was completed
@@ Line 195: / Line 193: @@
 </syntaxhighlight>
-It would then collect those handlers whenever an event is first dispatched to a gameObject, which should ultimately be only a small amount of extra overhead for more convenience. Any opinions?
+Whenever an event is first dispatched to a gameObject, it would collect the handlers by looking for methods which accept 1 event object and start with 'On', then pass them to addEventListener. That should ultimately be only a small amount of extra overhead for lots more convenience - Any opinions?

← Older revision		Revision as of 07:43, 15 April 2017
Line 195:		Line 195:
	</syntaxhighlight>		</syntaxhighlight>

−	It would ~~essentially~~ then collect those handlers whenever an event is first dispatched to a gameObject, which should ultimately be only a small amount of extra overhead for more convenience. Any opinions?	+	It would then collect those handlers whenever an event is first dispatched to a gameObject, which should ultimately be only a small amount of extra overhead for more convenience. Any opinions?

@@ Line 168: / Line 168: @@
 <syntaxhighlight lang="csharp">
-public class MyGameworldEvents : MonoBehaviour, IEvents{
+public class MyGameworldEvents : MonoBehaviour{
      [Handle("mousedown")]
@@ Line 184: / Line 184: @@
 <syntaxhighlight lang="csharp">
-public class MyGameworldEvents : MonoBehaviour, IEvents{
+public class MyGameworldEvents : MonoBehaviour{
      [Handle("missioncomplete")]
@@ Line 195: / Line 195: @@
 </syntaxhighlight>
-Any opinions?
+It would essentially then collect those handlers whenever an event is first dispatched to a gameObject, which should ultimately be only a small amount of extra overhead for more convenience. Any opinions?

← Older revision		Revision as of 07:33, 15 April 2017
Line 176:		Line 176:
	// and the UI was not.		// and the UI was not.

		+	}
		+
		+	}
		+	</syntaxhighlight>
		+
		+	The bonus being it would easily work with all of your custom events too:
		+
		+	<syntaxhighlight lang="csharp">
		+	public class MyGameworldEvents : MonoBehaviour{
		+
		+	[Handle("missioncomplete")]
		+	public void OnMissionComplete(MissionEvent e){
		+	// A mission was completed
		+	// and the event was dispatched to this gameObject.
	}		}