Backwards Compatibility

  • jacob1
    28th Oct 2012 Developer 0 Permalink
    @jacksonmj (View Post)
    Is that compiled with c++? Just wondering. It looks like it was. (not that that makes any difference at all, it doesn't)

    I'd also like to say that saves made with his version (and my mod) will have walls in the thumbnails. So use one of those if you want them in your save preview. They won't show the longer signs though.
  • Catelite
    28th Oct 2012 Former Staff 0 Permalink

    Why should we worry about backwards compatibility? What does C++ Powder Toy do at present that the current C version doesn't?

     

    There's obviously a ton of glitches yet to be fixed, but that's still a work in progress o.o

  • boxmein
    28th Oct 2012 Former Staff 0 Permalink
    @Catelite (View Post)
    There is a bad thing about backwards compatibility, it's what I like to call "innovation < compatibility". Garry's Mod, for example, is in the process of releasing version 13, which by Garry himself will break a lot of things. That way he can work freely and not push "safe" updates every now and then. I agree that it's important, but compatibility should not be top priority.
    that's a lot of -ity words there
  • jacob1
    28th Oct 2012 Developer 0 Permalink
    @Catelite (View Post)
    There are very few differences, but here is what jacksonmj's version changed:

    Fix wall loading from tpt++ saves *
    don't run clean_text on signs completely (but still limits length to 255)
    {t:15100|text} to open a forum thread
    Make sign editor textbox bigger

    Fix extra BUBW sometimes being produced when CO2 dissolves
    Fix DTEC not detecting photons
    don't let TNT flood fill explode when under other particles (prevents lag) *
    fix Newtonian gravity disappearing when reloading a save (with GRAVFFT enabled)
    Make conversion of PHOT to ELEC using BIZR, and enrichment of DEUT with ELEC, work better
    Decrease SPNG absorption chance, to make release of water from saturated SPNG look a bit less strange

    speed testing stuff (using benchmark argument when starting, and another for the file to test?)
    compatibility with g++, some other changes to allow this


    backwards compatibility isn't really something Simon needs to do, but for people that don't like tpt++, something like this needs to be done. (I think me and jacksonmj both still use our tpt++ compatible tpt versions). All we are doing is porting any new tpt++ changes back.

    I think tpt++ is almost fine, but it has some major glitches until the next version (tons of peoples stamps were deleted, and there are some crashes too), where many of the major ones will be fixed but not all. It's just missing tons of stuff that my mod has, my mod has many really cool and useful features that tpt++ doesn't. Me and a few other people use my mod for that reason. Other people don't like it because of the deco editor, it's harder to use (but easier than older tpt++ versions). It also looks different, the save browser just feels different, along with the whole thing. I think most changes about the looks are for the better, except for a few things, but maybe other people don't like it more.
  • NUCLER_FOX
    28th Oct 2012 Member 0 Permalink
    This post has been removed by jacksonmj: offtopic, use a conversation to contact a specific user about something unrelated to the thread