I had initially opted to  use x and y but I noticed that the property browser has built in support for "position" type data in the form of a QPointF. Using two seperate x and y values means that I would probably need to create a new enumerator for them.