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

Visual transparancy behavior on gazebo6 and default #1790

Closed
osrf-migration opened this issue Dec 1, 2015 · 8 comments
Closed

Visual transparancy behavior on gazebo6 and default #1790

osrf-migration opened this issue Dec 1, 2015 · 8 comments
Labels
all bug Something isn't working major rendering

Comments

@osrf-migration
Copy link

Original report (archived issue) by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).


I was recently trying to merge gazebo6 forward to default and I found some conflicts in Visual class. I tried resolving those conflicts in the gazebo6_to_default branch, which I think is pretty similar to @iche033 's derived_transparency branch from the declined pull request #1987, though I added and modified a couple expectations in the ChildTransparency portion of Visual_TEST.cc. There is currently one failing expectation in the test, though, at line 420.

It's one of the few places where SetTransparency is tested with cascade=false, and it's unclear to me what the expected behavior should be.

I discussed this with @chapulina a bit, but I'll step aside so the rendering masters can sort it out.

@osrf-migration
Copy link
Author

Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).


I forgot to mention I started a jenkins job for the gazebo6_to_default branch. It should confirm the failing expectation in UNIT_Visual_TEST.

@osrf-migration
Copy link
Author

Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).


The cascade parameter for transparency was added in pull request #1851, but maybe it doesn't make sense to ever set it to false.

@osrf-migration
Copy link
Author

Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).


test failure confirmed

@osrf-migration
Copy link
Author

Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).


Another build:

@osrf-migration
Copy link
Author

Original comment by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).


I decided to follow ogre's node api where cascade is always true for SetTransparency, and keep cascade option only for SetVisible. There is also a InheritTransparency function that allows users to control if children's transparency will be affected by the parent.

pull request #2031

@osrf-migration
Copy link
Author

Original comment by Steve Peters (Bitbucket: Steven Peters, GitHub: scpeters).


  • changed state from "new" to "resolved"

pull request #2031

@osrf-migration
Copy link
Author

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).


  • set version to "all"

@osrf-migration
Copy link
Author

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).


  • changed state from "resolved" to "closed"

@osrf-migration osrf-migration added major rendering bug Something isn't working all labels Apr 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
all bug Something isn't working major rendering
Projects
None yet
Development

No branches or pull requests

1 participant