Author Topic: Property Binding Editor conflicts with DFGUI  (Read 1785 times)

lzt120

  • Jr. Member
  • **
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 68
    • View Profile
Property Binding Editor conflicts with DFGUI
« on: June 10, 2014, 03:17:32 AM »
DFGUI has PropertyBindingEditor class which conflicts NGUI which also has the same class.

lzt120

  • Jr. Member
  • **
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 68
    • View Profile
Re: Property Binding Editor conflicts with DFGUI
« Reply #1 on: June 17, 2014, 08:17:05 AM »
for solve this problem, I think rename the class is one way.

ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: Property Binding Editor conflicts with DFGUI
« Reply #2 on: June 17, 2014, 10:33:31 AM »
Or choose one UI system and stick with it?

lzt120

  • Jr. Member
  • **
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 68
    • View Profile
Re: Property Binding Editor conflicts with DFGUI
« Reply #3 on: June 22, 2014, 02:24:47 AM »
In My current Project, need both of them. NGui for minimap and Hud and DFGUI is mainly for GUI

Nicki

  • Global Moderator
  • Hero Member
  • *****
  • Thank You
  • -Given: 33
  • -Receive: 141
  • Posts: 1,768
    • View Profile
Re: Property Binding Editor conflicts with DFGUI
« Reply #4 on: June 22, 2014, 05:36:01 AM »
Then you'll either have to locally change the name of one of the files, or put one of them in a namespace and make sure all the references to it still points right.

It's always dangerous when you have generic sounding names in the global namespaces because of issues like this, but NGUI stays there to stay compatible with old users. If everything moved to UI.NGUI namespace, then 100 % of projects would break until they change every reference to that, and it has been made clear that this is not wanted (much as I would like it. ;) )