FS Crashes when this module goes in toolbox

[billv]

Crashes everytime I try to put it in.(dragging in or right-click methods)

Module wont go into toobox.fsm

(63.66 KiB) Downloaded 1042 times

It's a Start/Stop circuit for a Drone Seq/Arp Seq/Host Seq module.
It's tested and working.
Tried dis-abling the Ruby parts before toolbox entry but same thing.

[trogluddite]

Ouch - never seen that before. Does the same here - had a tinker with a few things, but I couldn't make it go in without a crash.
I'd get that sent to the dev's if i were you - needs a serious looking into.

[trogluddite]

Gets weirder...

- Delete 'is Playing -' it goes in.
- Delete BOTH green links from 'Is Playing' (keep Ruby link) - it goes in.

Otherwise - always crashes. I tried removing the 'is playing' and putting a new one itn- still crashes; so seems to be a bug with that primitive - maybe be when they added to Ruby output something went wrong?

[tester]

That why I definately want to wait (a year or two?) before start to do anything with ruby.

[trogluddite]

What has Ruby got to do with it? It's just a random bug added while something was being updated- no different than the mistake made with the sine oscillators in the previous update. Are you going to stop using oscillators now too?
And the Ruby part of it seems fine - no problem leaving that connected, only the green links make it crash - maybe it's green triggers you should be avoiding?

Probably safest if we all just stop using Ruby entirely - then whatever bugs there are will never be found, and it will be untrustworthy forever!

[billv]

Ok. Modulize it and it goes straight in.
Fixes the issue BUT does not resolve it.
Support-Ball is in your court..

[billv]

That why I definately want to wait (a year or two?) before start to do anything with ruby

Animated Gif Simpson (101).gif (102.54 KiB) Viewed 21378 times

Cm 'on tester, jump in and drown like the rest of us.....

[tester]

Too many ruby-related random bugs / #strange @events seem to pop up right now . While bugs related to primitives are rather predictable and somewhat avoidable (due to sine bug, I switched into wavetables and learned about them), ruby is an open space of unknown interactions - i.e. too much is going on inside and around ruby, a really spooky virtual place. But this is my personal opinion, that's all. My split has a practical background - there are some projects, that I'd like them to work, with no excuses. BTW, if things wouldn't work, then I would switch the environment. I like you too Troggie . Besides in regards to ruby - I didn't say "never", I just said "right now". That makes a difference.

Programming is more an addiction than passion. I prefer to stay with my passion towards sound instead of addiction to green booleans flying up and around in my head when I close my eyes. That passion is strong enough to prevent me from becoming addicted.

[trogluddite]

addiction to green booleans flying up and around in my head when I close my eyes

He he - you know me too well! I sometimes look around my little 'computer den' and think some kind of junkie must live here!

At least the good thing is we are getting the updates nice and regular now - if that carries on, the Ruby gremlins will be sorted much faster than the old green/stream bugs used to be.
To be honest, with Ruby being so new, I was expecting far worse problems than we have seen. Maybe I just got lucky, but it has been very stable for me.

I like you too Troggie

Likewise - as with any friendship, the differences in temperament are better than always nodding in agreement to every opinion.

Ok. Modulize it and it goes straight in.

Very odd - seems like something graphics related - if you make a module, but set to reveal the GUI, it still crashes.

[billv]

Too many ruby-related random bugs / #strange @events seem to pop up right now

Your probably right. i just started with FS-Still don't know what I'm dealing with. I'm probably
crashing FS as many times as Nix is at the moment, trying to work it out.
Still lots to offer though without ruby:
Toolbox is unreal except for the viewing method.
Being able to change green stuff on the fly is just awesome.
Look forward to when they get the "libraries" happening as mentioned in User Guide.

green booleans flying up and around in my head

Don't know about Trog, but the only way i can shut my brain down is to put it to sleep.
There's always something flying around in there-may as well be a Green boolean or two

Very odd - seems like something graphics related - if you make a module, but set to reveal the GUI, it still crashes.

Could it be that it's dependant on being hooked up.? I mean, I have the GUI revealed in the Master module
and I can get that into the toolbox.?????....