Skip to content
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

Streamline edge selection #498

Merged
merged 2 commits into from
Oct 17, 2024
Merged

Conversation

arjxn-py
Copy link
Member

@arjxn-py arjxn-py commented Oct 17, 2024

Shall fix #478 & #482

edges.mov

Copy link
Contributor

github-actions bot commented Oct 17, 2024

Preview PR at appsharing.space

Copy link
Contributor

github-actions bot commented Oct 17, 2024

Integration tests repot: appsharing.space

@martinRenou
Copy link
Member

martinRenou commented Oct 17, 2024

This makes me think we should probably have some UI tests about selecting edges and applying edge operations. Let's do that in a separate PR!

@arjxn-py
Copy link
Member Author

This makes me think we should probably have some UI tests about selecting edges and applying edge operations. Let's do that in a separate PR!

Yes, that sounds good.

@@ -103,7 +103,7 @@ export class MainView extends React.Component<IProps, IStates> {
this._mainViewModel.renderSignal.connect(this._requestRender, this);
this._mainViewModel.workerBusy.connect(this._workerBusyHandler, this);

this._raycaster.params.Line = { threshold: 50 };
this._raycaster.params.Line2 = { threshold: 50 };
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am a bit confused by this.

  • I see it working properly in Firefox, just like in your screencast. So far so good, but we're not using Line2 in the codebase anymore, so why does it work?
  • I do not see it working in Chromium for some reason.

So should we explicitly use Line2 instead of Line for line meshes in the codebase so that it works in all cases? I would try that, but I really don't understand why it works in Firefox.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • I do not see it working in Chromium for some reason.

I haven't tested on firefox but I'm testing on Brave and Google Chrome and it both the cases it seems to work as expected on my end

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Weird!

Brave and Google Chrome are both chromium-based browsers. What's wrong with my chromium version 😅

Copy link
Member

@martinRenou martinRenou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Let's merge and iterate. I'll see if I can make it work on my chromium locally.

@martinRenou martinRenou merged commit 666255e into jupytercad:main Oct 17, 2024
10 of 11 checks passed
@arjxn-py arjxn-py deleted the edge-selection branch October 18, 2024 09:06
@martinRenou martinRenou added bug PR that fixes a bug enhancement New Feature or improvement and removed bug PR that fixes a bug enhancement New Feature or improvement labels Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug PR that fixes a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Selecting edges used to be easier
2 participants