Fix A Common Error Please

  • yotredwop92
    31st Mar 2013 Member 0 Permalink

    Instead of asking about suggestions, why don't you fix the common errors that come with the program.

     

    Like for starters, remove the stderr.txt and stdout.txt files that RANDOMLY appear every time you open it.

     

    And two, fix the problem with the program being UNABLE to close. I have tried closing it over 100 times now and it keeps telling me that the program has froze and is unable to close & that i need to wait for it to close.

  • Spock
    31st Mar 2013 Member 1 Permalink
    1: I don't recall them asking for suggestions.
    2: Why do rhey need to be removed?
    3: No files appear ranbomly when oppening.
    4: THe problem with closing sounds like it is only your computer.
    5: If it never closes, how are you here?
  • jacob1
    31st Mar 2013 Developer 1 Permalink
    this isn't common, i've never heard of anyone having that error before. So don't go saying a problem is common if you have never seen anyone have it before.

    try redownloading it, and run it from the .zip file. This will see if it's something with the powder.pref, stamps, or saves causing it.
    Also, does it crash when you just open and close it, or do you have to go into the save browser first or do any other activity to cause the crash on exit?

    And later, maybe try the beta 86.2 and see if it still crashes there.


    About the stdout and stderr, I was thinking about removing them but sometimes useful info goes in there. Maybe i'll think about it more , sometimes lua errors go in there and it's useful to some though.
    Also, stdout never gets deleted because of the error "could not open folder brushes/" or something, I don't like that error either, and removed it once, but then simon added it back. I might remove it again since it's not useful to 99.9% of people
  • yotredwop92
    31st Mar 2013 Member 0 Permalink

    @Spock (View Post)

     What I mean by it never closes is that the program will crash and remain in the crash screen, no matter how many times I use the "end process" command. The only way to get it to exit out is for me to log off or restart (and so on).

     

    As for stdout stderr I'm not entirely sure how they are useful, although I'm not a computer genius or anything; nor do I know a thing about programming, but I never figured a text file would be important to a program.

  • mniip
    31st Mar 2013 Developer 0 Permalink
    @yotredwop92 (View Post)
    well, as soon as someone sends many fixes to the dev team, admin decides to promote the user to a dev.
    and as soon as you're a dev, it's your job to fix the bugs, therefore your contribution is not noticed.
    just look at the https://github.com/FacialTurd/The-Powder-Toy/commits/master
    P.S on the bottom there's an 'older' button with even more commits
  • Shriek
    31st Mar 2013 Banned 0 Permalink
    This post is hidden because the user is banned
  • mniip
    31st Mar 2013 Developer 0 Permalink
    @Shriek (View Post)
    2. nope, antiviruses classify it as a virus because TPT has both downloading and system-level routines and that looks suspicious
    3. they don't pop *randomly*, they're created on launch, removed on closure
  • boxmein
    31st Mar 2013 Former Staff 0 Permalink
    @yotredwop92 (View Post)
    Basically, programs can be run in text consoles (COmmand Prompt) and in GUIs like 100% of the programs you use.
    Let's say TPT says something to the command prompt (Errors are often done like that, in a 'stream' called standard error) when it's a GUI program, what should it do? It'll forward everything to a file! Yes! Those two files aren't really used but they should be since they exist. Important stuff like logging and events and errors can be written there.

  • SuinDraw
    31st Mar 2013 Banned 0 Permalink
    This post is hidden because the user is banned
  • wes12321
    1st Apr 2013 Member 0 Permalink

    aren't stderr and stdout like the running files of the game? or are they just RAM space holders?