… and replaced the only usage of it with an equivalent call to Point class constructor.
@justalemon if you were planning to create lots more Point-based configuration properties in the future, there might be a better way to do this (e.g. by refactoring out the calculations out and passing a Tuple<x,y> around), but I'm assuming your UI stuff is nearly done ;)
… and replaced the only usage of it with an equivalent call to Point class constructor. @justalemon if you were planning to create lots more Point-based configuration properties in the future, there might be a better way to do this (e.g. by refactoring out the calculations out and passing a Tuple<x,y> around), but I'm assuming your UI stuff is nearly done ;)