Messages

16

NGUI 3 Support / NullReferenceException from NGUITransformInspector?

« on: February 13, 2014, 03:06:33 AM »

Been getting this error quite a lot recently even with the latest NGUI so I thought you should know about it.

1. NullReferenceException: (null)
2. UnityEditor.SerializedObject..ctor (UnityEngine.Object[] objs) (at C:/BuildAgent/work/d3d49558e4d408f4/artifacts/EditorGenerated/SerializedPropertyBindings.cs:69)
3. UnityEditor.Editor.GetSerializedObjectInternal () (at C:/BuildAgent/work/d3d49558e4d408f4/artifacts/EditorGenerated/EditorBindings.cs:117)
4. UnityEditor.Editor.get_serializedObject () (at C:/BuildAgent/work/d3d49558e4d408f4/artifacts/EditorGenerated/EditorBindings.cs:110)
5. NGUITransformInspector.OnEnable () (at Assets/External/NGUI/Scripts/Editor/NGUITransformInspector.cs:168)
6.  

It happens during editor-time - My console gets blown with +999 errors.

There's also the same error for GameObjectInspector too - "Inspector/GameObjectInspector.cs:91"

17

NGUI 3 Support / Re: How to get a List<EventDelegate> to work nicely with SerializedProperties?

« on: February 13, 2014, 03:04:03 AM »

Sorry if I'm asking a lot. But there's very little information about the subject and I'm trying to get the hang of editor scripting.

18

NGUI 3 Support / Re: How to get a List<EventDelegate> to work nicely with SerializedProperties?

« on: February 13, 2014, 01:16:05 AM »

Yes but in your editor scripts, sometimes you use target and manually register undo, sometimes just SPs and other times both! - Why don't you always use SPs and not manually register for undo, etc if they handle everything for you?

19

NGUI 3 Support / Re: How to get a List<EventDelegate> to work nicely with SerializedProperties?

« on: February 13, 2014, 01:11:24 AM »

Thank you!

If you don't mind please:

1- Generally speaking, are you saying that there's no way to convert a serializedProperty back to a List<SomeClass>? if there is, how? - Problem with using objectReferenceValue is that it's a UnityEngine.Object, and List is a System.Object. Do I have to wrap my list with a MonoBehaviour or something?
2- In this instance you suggested to use target, when do I know that it's safe to use target, and when should I always and must use SPs? because you're using a combination of both in your scripts :/

Thanks a lot!

20

NGUI 3 Support / Re: How to get a List<EventDelegate> to work nicely with SerializedProperties?

« on: February 13, 2014, 12:57:34 AM »

Sorry I still don't get what you mean:

1. NGUIEditorTools.DrawEvents("On Use", serializedObject, "onUse");
2.  

I just updated to the latest NGUI and still, there are only 2 DrawEvents:

1. static public void DrawEvents (string text, Object undoObject, List<EventDelegate> list)
2. static public void DrawEvents (string text, Object undoObject, List<EventDelegate> list, string noTarget, string notValid)
3.  

None of which takes a serializedObject as a 2nd parameter, and a string as third.

21

NGUI 3 Support / Re: How to get a List<EventDelegate> to work nicely with SerializedProperties?

« on: February 13, 2014, 12:20:36 AM »

you passed "onUse" as a string? is that a new overload for DrawEvents?

22

NGUI 3 Support / Re: How to get a List<EventDelegate> to work nicely with SerializedProperties?

« on: February 12, 2014, 10:51:27 PM »

Anybody?

23

NGUI 3 Support / How to get a List<EventDelegate> to work nicely with SerializedProperties?

« on: February 12, 2014, 02:50:22 AM »

Hello,

I have a "MonoBehaviour" with a "List<EventDelegate>" called "onUse" - In my custom editor, I just want to get a 'valid' reference to "onUse" via serialized properties, and then cast the property back to a List<EventDelegate> so that I could draw it - But I'm failing though.

I'm getting the property successfully:

1. sp_onUse = serializedObject.FindProperty("onUse");
2.  

But I don't know what to do here:

1. NGUIEditorTools.DrawEvents("On Use", use, ???);
2.  

On the side: I see in your editor scripts, sometimes you use SerializedProperties and other times you manually register for undo and use target instead. I can see two reasons why you would use target: 1- you wrote the editors before SerailizedProperties came about 2- (same reason I don't use SPs) SPs are very annoying, unpredictable and really tough to work with, debug, etc.

What approach you suggest I go forward with? stick with target and manually register undo, multiple edit, etc? or Wrestle with SPs?

Thanks a lot in advance.

24

NGUI 3 Support / Re: New anchoring system - very frustrating. Please explain it better.

« on: December 15, 2013, 02:34:06 AM »

Speaking of suggestions to make things better: I suggest to use a combination of both the ease of use of the old one, and the efficiency and power of the new one.

As a consumer here's how I'd love to see it happen:
I click on Anchor type | from that I get | TopLeft, TopRight, Center, Bottom, etc (Enum values) | click on one, and the widget would automatically anchor to that point (of course there would be a target field that gets automatically filled with the parent object like the new system does it) - after I anchor, there are 2 offset values I could change (much like the relative offset in the old one) - and I can also move the anchored widgets even if it's anchored much like in the new system.

I think that is much simpler as it avoids dealing with those cumbersome 4 values.

That is my humble opinion for "making the new system better"

25

NGUI 3 Support / New anchoring system - very frustrating. Please explain it better.

« on: December 14, 2013, 05:12:09 AM »

The new anchoring system overcomes the weaknesses in the old system and it does a better job than the previous Anchor+Stretch.

But it's really annoying in terms of practical usage - I mean, I just wanna anchor something to the top left corner of a background, it's just so tedious... What should I do with those 4 values? Previously, I just set the anchor to topleft and that's it. Now we have 4 values... what for? (I've seen the anchor demo video - but it just didn't cut it... )

Please explain what those four values mean - (what does it mean for the right of my object, to be in the right/center/left, etc of the target?)

I just have a very simple Colored slider that I want to anchor to the topleft of a background yet no matter how much I mess with the values, I can't seem to get the right ones....

Please explain.

Thanks.

26

NGUI 3 Support / Re: How to Create a modular clipped panel? (resizes correctly with its container)

« on: December 05, 2013, 06:10:07 AM »

OK - I found a good solution to my problem - It's OK to anchor the ScrollView (ClippedPanel) - But let the anchor only execute once. So that during the editing time we get full modularity - and then the anchor runs once when the game runs, does its thing, and deactivates - now scrolling works nice, no problems

27

NGUI 3 Support / Re: How to Create a modular clipped panel? (resizes correctly with its container)

« on: November 28, 2013, 10:49:08 PM »

If I don't anchor it, it wouldn't be modular anymore - which is the whole point here... How am I supposed to make it modular, without the anchoring?

28

NGUI 3 Support / Re: How to Create a modular clipped panel? (resizes correctly with its container)

« on: November 28, 2013, 01:54:17 AM »

I was so excited to check out the new clipping. Well it's here - Although clipping is now easier - much like a widget. But the issues remain the same - Scrolling is still messed up (unless I remove the UIAnchor) - And even more weird stuff is there as well! (Notice how in the beginning of the video, the panel was moving by itself! - I wanted to catch that on video, but managed to only get the end of it, it's .... alive! lol)- Though resizing still works well, much the same. I can't see how this clipped panel is any better than the old, besides the ease to change the clipped panel size like a widget.

Please watch this video: http://www.youtube.com/watch?v=1KV-c5NFjpM

You could easily reproduce what I have.

Hoping to see those issues resolved in the very near future, for GOOD.

Thanks.

29

NGUI 3 Support / Re: Atlases eternal doom. UIAtlas is not found, AtlasMaker is broken.

« on: November 28, 2013, 01:46:45 AM »

Guess not.

line 402 says: Texture tex = material.mainTexture;
line 250: if (mSprites.Count == 0) Upgrade();

30

NGUI 3 Support / Re: Atlases eternal doom. UIAtlas is not found, AtlasMaker is broken.

« on: November 28, 2013, 01:21:10 AM »

Alright I uploaded a shot of the error - check it out!