beach ball when setting degree to Nil

[eeeeaaii]

Hi, got a beach ball in the editor when setting degree to Nil.

screen shot of code attached. I also got this error:

Error in Player a1: float() argument must be a string or a number, not 'function'

[Qirky]

When you say beach ball, do you mean it crashes / becomes unresponsive? This doesn't happen on Windows, so it might my MacOS related. What version of Python are you using? As for the error message, that's the intended output. Nil is a function defined in FoxDot.lib.Patterns.Operators defined as follows:

def Nil(a, b):
    return a

Inputs can't be functions, so instead of crashing the application, FoxDot prints that error message then tries to play the next event. What are you trying to do by setting the degree to "Nil"? I would suggest using a1.stop() if you want to not play anything, or use a1.degree = 0 if you want to set it back to it's original value. You can also use ~a1 or a1.reset() to all

[eeeeaaii]

I was trying to get it to stop differently... i.e. to play through the rest of the loop instead of hard-stopping immediately...

…

On Tue, Jun 29, 2021 at 4:13 PM Ryan Kirkbride ***@***.***> wrote: When you say beach ball, do you mean it crashes / becomes unresponsive? This doesn't happen on Windows, so it might my MacOS related. What version of Python are you using? As for the error message, that's the intended output. Nil is a function defined in FoxDot.lib.Patterns.Operators defined as follows: def Nil(a, b): return a Inputs can't be functions, so instead of crashing the application, FoxDot prints that error message then tries to play the next event. What are you trying to do by setting the degree to "Nil"? I would suggest using a1.stop() if you want to not play anything, or use a1.degree = 0 if you want to set it back to it's original value. You can also use ~a1 or a1.reset() to all — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#247 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE2T4E35J2STALH4OOJW53TVISPTANCNFSM47MSJ7FQ> .

[Qirky]

So for each attribute, e.g. degree, duration, amplitude, there is a separate 'loop' if that makes sense. So there isn't a way to stop it after "complete loop" because that doesn't exist. However, you can use .after(n, <str:method> to call "stop" after n number of beats e.g.

p1 >> pluck([0, 1, 2], dur=1/2, amp=[0,1,1,0,1]).after(4, "stop")

[eeeeaaii]

ah ok thanks!

…

On Wed, Jun 30, 2021 at 1:14 PM Ryan Kirkbride ***@***.***> wrote: So for each attribute, e.g. degree, duration, amplitude, there is a separate 'loop' if that makes sense. So there isn't a way to stop it after "complete loop" because that doesn't exist. However, you can use .after(n, <str:method> to call "stop" after n number of beats e.g. p1 >> pluck([0, 1, 2], dur=1/2, amp=[0,1,1,0,1]).after(4, "stop") — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#247 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE2T4AENMDXK43P4IEGY5DTVNGGDANCNFSM47MSJ7FQ> .