FUZE 3.0.0 IS HERE!


  • F

    Awesome. Fixed the bug with deep loops with arrays. Got me with my sloppy programming habits ( but overloading functions will stop that , no more commenting code out to try something different ). And search omg I'm in heaven.
    Absolutely the best patch yet. Now to find the time...


  • F

    ‘Deep loops with arrays’?


  • F

    @toxibunny yeah.
    Nested loops with a loop 3 or 4 deep that accessed an array didn't access the array unless I did a work around . I wrote about it somewhere after the last update because that's what broke it.


  • F

    @xevdev
    In wormhole I was loading my own models in and they worked fine except for a few that I used a different method that I calculated on the fly. This used an array for the points and found a work around by making another New array and using that.
    However my muck around program in which I was joining models together to make the liberator from Blake's 7 also suffered from this problem since the previous update. Which was frustrating since I'd spent some time juggling it all in my head to get it to work to see the update render it useless. Almost immediately after I'd done it.
    Picked up fuze today took 2 minutes to fix the other issues ( overloading functions would have made them irrelevant). And it worked again. Without changing the code loops. Yay !!!!


  • F

    Just want to say I really think the new error messages (stack trace) in 3.0.0 make it easier to track down problems now, So thanks for that.


  • Fuze Team

    You're welcome! I'm looking forward to making stack traces even better in the future.



  • I also would like to say that the new update greatly increased my enjoyment and productivity. Refactoring code is now feasible!


  • F

    What is it that has made the difference?



  • For refactoring, search & replace, clearly. And callstacks! They allow to write smallish functions that call one another without ending up with an error deep down where it's clear that the function just has been called with some wrong parameters, then having to find the source, only to discover it also was called with wrong parameters... These two together enable fearless changes.
    Next one is that multline pasting no longer messes up :) I also use quickfind a lot to see where I access some variable or use a function, and I quite like that calling functions that don't exist now is an immediate error.


  • F

    @Z-Mann The call stack saved me probably thirty minutes of debugging yesterday-- wonderful feature. Like you, I'm constantly using the quick find / jump to function features, to the point where I'm not sure how I functioned before them: "L" and "R" are my best friends now.


Log in to reply