#Layouteditor moveby code

tPos(newPos) / Position the mouse in it's parent coordinate system : (10, 12) so on. tPos(newPos) / Position the mouse in it's parent coordinate system : (10, 11) / The 'myMouse' coordinate in scene coordinates are (10,10).Ī call myMouse.mapToParent(0,0) will return (10,10) Ī call myMouse.mapToParent(0,1) will return (10,11) Īnd this is the /* Position the mouse in it's parent coordinate system : (10, 10) /.

The 'myMouse' local coordinates are (0,0), i.e origin of the mouse item.

The 'mapToParent' function converts a coordinate in item coordinates to coordinate in parent's coordinate system (or scene coordinates if no parent)įor example, if you have a mouse 'myMouse' at (10,10) in your scene: The confusion does not come from your interpretation of 'setPos' (which acts as you expect), but from the 'mapToParent' function Everytime advance is called, the item is 'moved by' (0,1) I also saw another function somewhere else that works exactly the same way (Correct me if I am this seems intuitive to me. However, it seems this causes the item to move with a constant acceleration. I expected to see something move something downwards, with ypos incremented in 'advance' member function in QGraphicsItem.

#Layouteditor moveby code

I had to rummage though the code to figure out what was moving the QGraphicsItem. (This is not part of the code, but I modified the 'setPos' function slightly to see how it works) It took me several days to figure a QGraphicsItem downwards, everytime 'advance' (QGraphicsView function) is called. I looked at the 'colliding mouse example': that ships with Qt.