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
This is nothing new, but maybe we could improve a way in which elements are moved in the preprocessor panel. I get used to ++ (it is definitely not intuitive for beginners).
This time I'd like to write about implementation of moving algorithm, which makes object moves "delayed" comparing to the mouse pointer.
It is only my guest, but it seems that Agros2D is using MouseMove event, which is not to precise about relative location of the mouse pointer. It shoud be more accurate to store original location of the mousePress event, and calculate difference from current coordinates. Does it make sense?
The text was updated successfully, but these errors were encountered:
I'll try to implement it. It seems to be less "delayed".
Pavel
On 28.5.2014 00:49, Bartosz Sawicki wrote:
This is nothing new, but maybe we could improve a way in which
elements are moved in the preprocessor panel. I get used to ++ (it is
definitely not intuitive for beginners).
This time I'd like to write about implementation of moving algorithm,
which makes object moves "delayed" comparing to the mouse pointer.
It is only my guest, but it seems that Agros2D is using MouseMove
event, which is not to precise about relative location of the mouse
pointer. It shoud be more accurate to store original location of the
mousePress event, and calculate difference from current coordinates.
Does it make sense?
—
Reply to this email directly or view it on GitHub #125.
This is nothing new, but maybe we could improve a way in which elements are moved in the preprocessor panel. I get used to ++ (it is definitely not intuitive for beginners).
This time I'd like to write about implementation of moving algorithm, which makes object moves "delayed" comparing to the mouse pointer.
It is only my guest, but it seems that Agros2D is using MouseMove event, which is not to precise about relative location of the mouse pointer. It shoud be more accurate to store original location of the mousePress event, and calculate difference from current coordinates. Does it make sense?
The text was updated successfully, but these errors were encountered: