EQInterface Forums - View Single Post - I wish.... allow 'overloading'

Going to have to disagree with you on this one. By allowing what you are requesting, you are limiting compatibility between different UIs, and basically gives the end user a work around for sloppy programming.

By learning the correct interaction between the windows, with correct name conventions, etc., you can create a product that will work with other peoples work.

For example,
Bars.xml has the casting gauge in it. What is the person is using Turlo's Casting Window? All of a sudden, you have two casting guages in the same directory. The result would cause it to crash to desktop, and well it should.

If the designer of Bars.xml used Bars_Casting_Gauge as the piece utilized within the window, the naming conventions are kept seperate, and there is no compatibilty problem with other components.

06-30-2004, 09:20 PM	#2
Turlo Featured Artist Join Date: Aug 2002 Posts: 317	Going to have to disagree with you on this one. By allowing what you are requesting, you are limiting compatibility between different UIs, and basically gives the end user a work around for sloppy programming. By learning the correct interaction between the windows, with correct name conventions, etc., you can create a product that will work with other peoples work. For example, Bars.xml has the casting gauge in it. What is the person is using Turlo's Casting Window? All of a sudden, you have two casting guages in the same directory. The result would cause it to crash to desktop, and well it should. If the designer of Bars.xml used Bars_Casting_Gauge as the piece utilized within the window, the naming conventions are kept seperate, and there is no compatibilty problem with other components. __________________ "Ah, but you HAVE heard of me."