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

Bug? Particles2D.one_shot = true does not set emitting to false like in 2.1.4 #12218

Closed
ericrybick opened this issue Oct 18, 2017 · 3 comments
Closed

Comments

@ericrybick
Copy link
Contributor

I'm not sure if this is intended or a bug.

As the title says, when using Particles2D.one_shot=true the emission gets stopped (visually), but the emitting bool stays true.

@cbscribe
Copy link
Contributor

cbscribe commented Dec 1, 2017

I noticed this is labeled "discussion", so I'll chime in.

"One_shot" is useful for limited emissions you want to trigger at a certain time. You may want to queue_free() upon completion, or trigger another emission but only if one isn't currently occurring.

Without "one_shot" setting emitting to false upon completion of the emission cycle, and no "emission_finished()" signal, we can't tell if a one-shot emission has ended.

@reduz
Copy link
Member

reduz commented Dec 6, 2017

it does, but it's not visualized in the editor. It's kind of a hassle if you want to animate it.
I will prefer we wait until 3.1 when the property editor is reworked to fix this properly, so kicking

@reduz reduz modified the milestones: 3.0, 3.1 Dec 6, 2017
@cbscribe
Copy link
Contributor

cbscribe commented Dec 6, 2017

it does, but it's not visualized in the editor.

I don't think that's true. I just tested it, and on a one-shot Particles2D node, print(emitting) continues to print "True". See attached.

particles_oneshot.zip

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

No branches or pull requests

4 participants