Navigation

    Fuze Arena Logo
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Popular
    • Users
    • Groups
    • Help
    • Discord

    FUZE 3.0.0 IS HERE!

    Announcements
    10
    18
    1126
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • xevdev
      xevdev F last edited by

      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...

      1 Reply Last reply Reply Quote 6
      • PickleCatStars
        PickleCatStars F last edited by

        ‘Deep loops with arrays’?

        xevdev 1 Reply Last reply Reply Quote 0
        • xevdev
          xevdev F @PickleCatStars last edited by

          @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.

          xevdev 1 Reply Last reply Reply Quote 0
          • xevdev
            xevdev F @xevdev last edited by

            @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 !!!!

            1 Reply Last reply Reply Quote 4
            • SteveZX81
              SteveZX81 F last edited by

              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.

              1 Reply Last reply Reply Quote 5
              • Willpowered
                Willpowered Fuze Team last edited by

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

                1 Reply Last reply Reply Quote 6
                • Z-Mann
                  Z-Mann last edited by

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

                  1 Reply Last reply Reply Quote 5
                  • PickleCatStars
                    PickleCatStars F last edited by

                    What is it that has made the difference?

                    1 Reply Last reply Reply Quote 0
                    • Z-Mann
                      Z-Mann last edited by

                      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.

                      Spacemario 1 Reply Last reply Reply Quote 2
                      • Spacemario
                        Spacemario F @Z-Mann last edited by

                        @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.

                        1 Reply Last reply Reply Quote 4
                        • First post
                          Last post