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

Document CollisionObject2D pickable requires collision_layer #28552

Closed
wants to merge 2 commits into from
Closed

Document CollisionObject2D pickable requires collision_layer #28552

wants to merge 2 commits into from

Conversation

lopho
Copy link
Contributor

@lopho lopho commented May 1, 2019

Document CollisionObject2D signals mouse_entered, mouse_exited and input_event require at least one collision_layer to be set.

Sadly, collision_layer is implemented, and thus documented in the child classes Area2D and PhysicsBody2D (why not in the parent class?), so this might be a source of confusion.

Clarifies #11159

@lopho lopho requested a review from a team as a code owner May 1, 2019 01:10
@akien-mga akien-mga added this to the 3.2 milestone May 1, 2019
@mhilbrunner
Copy link
Member

Thank you!

[\code] should be [/code] instead.

Copy link
Member

@mhilbrunner mhilbrunner left a comment

Choose a reason for hiding this comment

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

Change [\code] to [/code]

@lopho
Copy link
Contributor Author

lopho commented May 1, 2019

Sorry, stupid typo + copy paste. Fixed.

@mhilbrunner
Copy link
Member

No worries, thanks for the fix! Can you squash your commits into one?

aqnuep and others added 2 commits May 2, 2019 03:49
The bake mode property of lights previously didn't affect GI probes.
This change makes the GI probe ignore lights that have their bake mode
set to disabled.
Documents CollisionObject2D mouse_entered, mouse_exited and input_event requiring at least one collision_layer to be set.
@lopho lopho requested a review from reduz as a code owner May 2, 2019 01:52
@lopho
Copy link
Contributor Author

lopho commented May 2, 2019

Sheesh, I seem to be not up to par today, sorry. I messed that squash up as well. oh boy...
Or not? I'm confused, why has my rebase pulled the previous commit (5c84a64) into this PR?

@mhilbrunner
Copy link
Member

mhilbrunner commented May 2, 2019

Again, no worries! I had to get used to the GitHub workflow too :)

Maybe this can help:
https://stackoverflow.com/questions/36168839/how-to-remove-commits-from-a-pull-request

If it doesn't, if you want you can also close this PR and submit the (intended) changes as a new PR :)

@lopho
Copy link
Contributor Author

lopho commented May 2, 2019

Yeah, I'm not used to squashing. I'll open a new PR, messing around with this PR for 3 lines is wasted time.

@lopho lopho closed this May 2, 2019
@lopho lopho deleted the patch-1 branch May 2, 2019 13:36
@lopho
Copy link
Contributor Author

lopho commented May 2, 2019

new PR: #28608

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

Successfully merging this pull request may close these issues.

5 participants