Skip to content

constraint colors #7647

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

Open
wants to merge 20 commits into
base: main
Choose a base branch
from
Open

constraint colors #7647

wants to merge 20 commits into from

Conversation

Irev-Dev
Copy link
Contributor

@Irev-Dev Irev-Dev commented Jul 1, 2025

Screenshare.-.2025-07-01.5_30_38.PM.mp4

Copy link

vercel bot commented Jul 1, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
modeling-app ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 21, 2025 6:15pm

@Irev-Dev Irev-Dev marked this pull request as ready for review July 1, 2025 09:45
@Irev-Dev Irev-Dev requested a review from a team as a code owner July 1, 2025 09:45
Copy link
Contributor

@pierremtb pierremtb left a comment

Choose a reason for hiding this comment

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

I think it's a great idea to make it feel a little more like SW! Things don't seem super stable locally for me, especially when the path is closed, see video and the errors about close. Happy to help reproduce if you have specific things I should try

Screen.Recording.2025-07-01.at.11.46.50.AM.mov

@Irev-Dev
Copy link
Contributor Author

Irev-Dev commented Jul 2, 2025

Thanks @pierremtb I think I solved it?

The noise is gone, but I never had trouble with the segments not getting coloured correctly so not sure, maybe it was your sketch, either way could you try it again?

Copy link
Contributor

@pierremtb pierremtb left a comment

Choose a reason for hiding this comment

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

I think I can trigger it by clicking around and moving segments, it's like something gives up at some point?

Screen.Recording.2025-07-02.at.12.04.29.PM.mov

callExpName?: string
isFullyConstrained: boolean
}): number {
if (isSelected) return 0x0000ff // Blue for selected
Copy link
Contributor

Choose a reason for hiding this comment

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

Doesn't have to be in this PR: I was thinking about the two different blues we have now on this branch: zoo blue for unconstrained, and that full blue for selected.

So I went looking at other apps and Onshape uses their 'selection' color to show selected segments, which is the same color as when they select faces. I think that makes a ton of sense right? Same color for us as highlighted code or scene selection would be dope here

image

Copy link
Contributor Author

Choose a reason for hiding this comment

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

There's only two blue becaue I use the "primary color" for the unconstrained blue, which is blue by default, but you can see it's orange in my vid in the PR description.

That's really just a side note though, maybe I'll make hover and selected two shades of yellow, since that's what's selected is engine side. Good suggestion.

Copy link

vercel bot commented Jul 18, 2025

Deployment failed with the following error:

You must set up Two-Factor Authentication before accessing this team.

View Documentation: https://vercel.com/docs/two-factor-authentication

@Irev-Dev Irev-Dev requested a review from pierremtb July 18, 2025 09:45
Copy link
Contributor

@pierremtb pierremtb left a comment

Choose a reason for hiding this comment

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

Recording.2025-07-18.132008.mp4

@Irev-Dev I'm wondering if I'm just running into perf issues here on windows? I keep hitting blinking colors and I'm afraid that could be more confusing than helpful? Potentially could be worth rebasing once @andrewvarga 's PR gets in and seeing if that makes a difference?

I pushed a fix for npm tsc btw, should be back to green

@Irev-Dev
Copy link
Contributor Author

I'm wondering if I'm just running into perf issues here on windows?

@pierremtb Hmm that is pretty annoying. I think it's more likely to be a race made worse by perf perhaps. I haven't been able to replicate it. But I agree don't want to merge unless it's consistent. I did make one more commit that could be the source of a race, where colors were only applied on update not create (I had thought this was good to keep things simple with how much some extra params need to be passed around, but possible the update is not getting called sufficiently when there'se perf issues not sure.) so if you wanted you could try it again?

I pushed a fix for npm tsc btw, should be back to green

Thank you.

@pierremtb
Copy link
Contributor

@Irev-Dev Thanks, bummer we keep delaying this. I did have a look quick on my mac here, and can still reproduce. But only in electron (npm run tron:start) and not in Chrome (npm run start), the latter is something I haven't tried before with this branch. I think you're developing more in the web env, is that right? If so, any chance you could try to reproduce in the electron environment?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants