New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to add a vertex to a collision mask by pulling an edge. #4778
Conversation
UX frictions identified during individual testing to consider: On Mobile:
Question: do we still need the drag for XY lines? It was there to re-order vector position, but I'm not entirely sure that they should be there anymore (in order to prioritise a visual, over a numeric Interface). Uncertainties to observe during tests (on recruiting status):
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, just a few comments
/** | ||
* @returns true if the vertex should be deleted. | ||
*/ | ||
const magnetDraggedVertexForDeletion = (): boolean => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this function should have a clearer name to say what it does.
But it's confusing because it does both "update the draggedVertex" and "say if it should be deleted"
maybe call it updateMagnetDraggedVertexForDeletion()
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I though is was a verb, I'll replace it with "magnetize".
@@ -127,32 +270,45 @@ const CollisionMasksPreview = (props: Props) => { | |||
/> | |||
); | |||
})} | |||
{mapVector(polygons, (polygon, i) => { | |||
{mapVector(polygons, (polygon, polygonIndex) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
way clearer thanks
@@ -43,7 +43,7 @@ const horizontalMosaicNodes: EditorMosaicNode = { | |||
direction: 'row', | |||
first: 'preview', | |||
second: 'properties', | |||
splitPercentage: 50, | |||
splitPercentage: 66.67, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this look fine on all resolutions? (+mobile?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On mobile, it uses the vertical layout. Even with a 1,000 pixels wide window, it seems ok. It allows a bigger image.
Vector Wokspace - User testing 7/01/2023 (Thanks @roshh and @beanmatt for your valuable input!):
Other findings:
To do:
Nice to haves:
|
http://gdevelop-storybook.s3-website-us-east-1.amazonaws.com/pull-new-vertex/latest/index.html?path=/story/objecteditor-spriteeditor--collision-masks