Page 1 of 2
display error
Posted: Sat Jul 05, 2014 10:32 am
by rustyou
Hello,
I've a calcul who display the error : 1.#INF
Because the calcul is : 0/0 . this is normal
But for the user, i would like display 0 .
How shall we do it?
Thanks
Re: display error
Posted: Sat Jul 05, 2014 10:57 am
by Drnkhobo
Re: display error
Posted: Sat Jul 05, 2014 10:59 am
by TheOm
Very simple. Just check if the result is infinity and use a selector to display 0 instead.
Re: display error
Posted: Sat Jul 05, 2014 11:28 am
by rustyou
Oh yes perfect thank you.
And for the flaot.
I want to display just one 0 for the user and no 0.0. But i want to display the decimal too....?
Re: display error
Posted: Sat Jul 05, 2014 12:08 pm
by TheOm
Like this?
Re: display error
Posted: Sat Jul 05, 2014 12:34 pm
by tester
@TheOm - can you check if you can open your last schematic by double clicking on it?
It's one of these cool examples, that crash Flowstone.

BTW, if it crashes on your machine as well - send it to support.
Re: display error
Posted: Sat Jul 05, 2014 4:33 pm
by rustyou
Yes great

thank you for your help TheOm
Re: display error
Posted: Sat Jul 05, 2014 5:29 pm
by TheOm
tester wrote:@TheOm - can you check if you can open your last schematic by double clicking on it?
It's one of these cool examples, that crash Flowstone.

BTW, if it crashes on your machine as well - send it to support.
Sorry can't check. I'm using the FL-Studio plugin version, so I always have to use the Open-File dialog.
Re: display error
Posted: Sat Jul 05, 2014 7:52 pm
by tester
Okay, I sent it to Malc.
This is one of these situations in which when you start the schematic by double click on it (i.e. not drag and drop to FS nor load via menu) - it crashes FS. I checked on two machines and is the same. Appearently it has to do with some sort of initialization order between FS guts and ruby.
@Nubeat7 - it's one of these spooky scenarios I talked about. Probably will be fixed with the next release.
Re: display error
Posted: Sat Jul 05, 2014 8:55 pm
by Nubeat7
tester wrote:@Nubeat7 - it's one of these spooky scenarios I talked about. Probably will be fixed with the next release.
no idea what you are talking about? everything works normal here...