about EventDalegate drawer/editor

[gyd]

1. Could the EventDalegate support constant input ( intField/floatField/.. ) too?
2. Could the EventDalegate select menu sort when show?

[ArenMook]

1. I haven't added support for that.
2. I am not sure what you mean.

[gyd]

as image.

[ArenMook]

Sure, open EventDelegateDrawer.cs and add this on line 86:

1. list.Sort(delegate(Entry a, Entry b) { return a.name.CompareTo(b.name); });

[gyd]

of course i could add it by myself, but what i post is a suggestion.

[ArenMook]

I've added it to 3.9.4.

[gyd]

I've added it to 3.9.4.

thanks for the support

[gyd]

sorry to pop this thread up, in the 3.10, the constant support is still not added.

i've posted an example here : http://www.tasharen.com/forum/index.php?topic=12781.msg57959#msg57959 ( but i dont think my code is good to use directly ).
is there a plan to add the constant support of EventDelegate?

[ArenMook]

Hmm... I'm not sure why I never did. I'll look into it, thanks for the reminder.

[gyd]

thanks!! it is surely a good news!

[ArenMook]

Ok, now I remember why I didn't do it.

I couldn't get the PropertyDrawer to work (EventDelegateDrawer). Unity's SerializableProperty can't serialize "object" type fields. It has to have an explicitly recognized value such as int, float, Vector3, etc.

So in order to get this to work, the EventDelegate.Parameter would need to have fields for all the types Unity understands -- string, int, Color, all of them. One for each. Only then is it possible to get them serialized. Of course doing so also bloats the size of the data dramatically, which is why I didn't do it.

If I'm wrong, and you somehow manage to get it to work with just an "object" field, I'd love to have a look at your implementation.

[gyd]

edit:
yes you are right, if we want to store params by constant value, we need to list all of the values.

but i tested it, each variable needs 38 bytes to store when meta is in text mode, and 360 bytes in binary mode.
maybe it dont bloat so dramatically, could you consider it? that would make the workflow much simpler.

[ArenMook]

It not only bloats memory usage but also the code. What is your workflow that requires passing static values?

[gyd]

a simple example is like:

a player selection menu with 4 players button, and when a button is pressed, call a method to set the players in the game.

current :

1. // we need to add new apis for new settings, like Set5Player
2. public void Set1Player(){ players = 1; }
3. public void Set2Player(){ players = 2; }
4. public void Set3Player(){ players = 3; }
5. public void Set4Player(){ players = 4; }
6.  
7. // or
8. // add to a script
9. public int intValue = 0;
10.  
11. // and add this to a manager / singleton, then drag and assign the intValue to the control eventDelegate
12. public void SetPlayers( int i ){ players = i; }
13.  

after :

1. // and add this to a manager / singleton, then just set the value is needed directly in inspector
2. public void SetPlayers( int i ){ players = i; }
3.  

[ArenMook]

You can simply name your buttons 1, 2, 3 and 4 -- then do

1. void SetPlayers ()
2. {
3.     int.TryParse(UIButton.current.name, out players);
4. }