-
Notifications
You must be signed in to change notification settings - Fork 32
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
Make model marker less shiny #1140
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@jimmyDunne If you review and merge will get an Artifact of the gui with integrated fix. |
James, the wrong shading suggest this build of the gui does not have the
core fix. I can restart the gui build to force that unless you locally
built latest master on both core and gui.
…On Thu, Oct 3, 2019, 6:31 AM jimmyDunne ***@***.***> wrote:
They are definitely different. I have a few comments just as impressions
as I looked at it for the first time.
From a not-so-far distance away, the markers appear more 'black' than pink.
[image: image]
<https://user-images.githubusercontent.com/5296507/66130552-e2e9d400-e5bf-11e9-8e2a-fa3c554c53ac.png>
If I would have to guess, it may because the dark shading on the marker is
on the superior surface of the maker, rather than than the infererior. The
experimental markers seem to have the darker shading on the inferior
surface of the sphere, which we may want to mimick. I think that would help
the Model marker pinl coloring to stand out.
[image: image]
<https://user-images.githubusercontent.com/5296507/66130814-5d1a5880-e5c0-11e9-9dc6-78aad0a49bd5.png>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1140?email_source=notifications&email_token=AA6JY4DVRPNM6YAH6FRUKXDQMXXZLA5CNFSM4I35TVY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAIGVDI#issuecomment-537946765>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA6JY4AB5J56IPY2ZPJ4DATQMXXZLANCNFSM4I35TVYQ>
.
|
I don't build the GUI locally so if you could force another CI build I can get the artifact? |
Thanks @jimmyDunne Artifact of master is ready to test. Sorry about the confusion |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes issue #1107
Brief summary of changes
Change material specification of model markers to match those of experimental markers for consistency. Along with opensim-core fix to scale factors these two fixes combined result in better looking model markers.
Testing I've completed
Created new markers, loaded models with markers and inspected visualization
CHANGELOG.md (choose one)
-updated