You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When programming in C# sometimes you'll import System for maybe using C# Math or to throw certain built-in exception types.
However, if you're wanting to export a Range on your node object (for a progress/stat indicator for instance), this can cause a conflict as there'll now be two Range types in scope...
error GD0102: The type of the exported property is not supported: 'Project.Display.FuelBar'
error CS0104: 'Range' is an ambiguous reference between 'Godot.Range' and 'System.Range'
Other .NET UI frameworks usually use RangeBase as their base abstract construct for this type of class.
Would it make sense in a future major version to change Godot.Range to Godot.RangeBase to avoid the conflict with the built-in C# class?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When programming in C# sometimes you'll import
System
for maybe using C#Math
or to throw certain built-in exception types.However, if you're wanting to export a
Range
on your node object (for a progress/stat indicator for instance), this can cause a conflict as there'll now be twoRange
types in scope...Other .NET UI frameworks usually use
RangeBase
as their base abstract construct for this type of class.Would it make sense in a future major version to change
Godot.Range
toGodot.RangeBase
to avoid the conflict with the built-in C# class?Beta Was this translation helpful? Give feedback.
All reactions