NGUI 3.5.6 Code conflict with uFrame!!!

[PanCotzky]

Hi!

I've encountered a problem that almost destroyed two months of my work. I'm using uFrame data binding engine (https://www.assetstore.unity3d.com/#/content/14381) as well as NGUI. 90% of my code uses uFrame. After updating NGUI I've got a conflict in their codes: PropertyBinding class is declared in both uFrame and NGUI. And as none of them uses namespaces, that means that I can't use them both at the same time. Thanks God I saved an older version of NGUI and reversed to it. But I hope you will solve this problem. I've already wrote to uFrame developers about this problem. May be you should cooperate with each other.

[ArenMook]

Can't say I've ever heard of uFrame, and it's a terrible name for a data binding framework if it's truly all it does.

You can modify your local copy of 3.5.6 to put NGUI's PropertyBinding into its own namespace if you like. You will just need to clarify which property binding is used like so:

1. using PropertyBinding = CustomNamespace.PropertyBinding;

...assuming "CustomNamespace" is what you called the namespace. The line above will need to be placed in the following 3 files:
* NGUIContextMenu.cs
* NGUIHelp.cs
* PropertyBindingEditor.cs

[PanCotzky]

But as I understand the PropertyBinding class used all across NGUI and I not only have to implement a namespace for the entire NGUI. I also have to do this EVERY time I update NGUI, haven't I?

[ArenMook]

Property binding is a stand-alone component and is only used in those 3 files I mentioned.