Jump to content


Photo

About removal of Errors tab


  • Please log in to reply
12 replies to this topic

#1 alexandervrs

alexandervrs

    GMC Member

  • GMC Member
  • 423 posts
  • Version:GM:Studio

Posted 15 May 2012 - 06:29 PM

I yet posted another bug report, this time for the removal of the "Errors" tab.
First of all, I don't mind the overall removal of the tab, actually I never used the logging to the game_errors.log etc. but I did use the "Display error messages" option.

I would usually turn it off, because I wanted a custom error message in case something went wrong,
For example I could do professional error reporting like,

if (error_occured) {
    if (show_question("An error occurred. Would you like to send a report to the developer?")) {
       //send "error_last" string with some game info using http_post_string or http_get, or just open url with bug report form
   }
}

and also protect any code snippet from being exposed, there's no need the player to know the error that occurred in what object. They are not coders, nor is their business.
But they can report it or have meaningful error messages shown to them. And the developer of the game should be in charge of that.

I would like to urge you to please reconsider adding back the "Display error messages" option (Maybe in the General tab) and now deprecated error_last, occurred variables (maybe in the form of functions? error_get_last() error_occurred()? ).
I don't believe they are that much of an overhead and were really an underrated feature.

This overall gives a much better user experience and helps GameMaker and our games look much more professional. :)

Edited by alexandervrs, 15 May 2012 - 06:32 PM.

  • 1

#2 Graphic Galore!

Graphic Galore!

    GMC Member

  • New Member
  • 68 posts
  • Version:GM8

Posted 15 May 2012 - 06:32 PM

Hmmm...
  • 0

#3 rwkay

rwkay

    YoYo Games CTO

  • YoYo Games Staff
  • 1415 posts
  • Version:Unknown

Posted 15 May 2012 - 06:38 PM

I shall discuss this with Mike tomorrow - your point is valid.

Russell
  • 2

#4 alexandervrs

alexandervrs

    GMC Member

  • GMC Member
  • 423 posts
  • Version:GM:Studio

Posted 15 May 2012 - 06:39 PM

I shall discuss this with Mike tomorrow - your point is valid.

Russell


Thanks for listening :)
  • 0

#5 Pstadler

Pstadler

    GMC Member

  • GMC Member
  • 58 posts

Posted 29 May 2012 - 02:52 PM


I shall discuss this with Mike tomorrow - your point is valid.

Russell


Thanks for listening :)


So, what now? I really need the "Show errors" function. And what about the "Thread uninitialized values as zero" function? Thanks!
  • 0

#6 alexandervrs

alexandervrs

    GMC Member

  • GMC Member
  • 423 posts
  • Version:GM:Studio

Posted 29 May 2012 - 04:41 PM

"Treat uninitialized values as zero" has been completely removed, this won't be coming back as it caused problems in several platforms.
You should initialize properly any variables you will need.
  • 0

#7 @Alex@

@Alex@

    Retired GMC Reviewer

  • Reviewer
  • 3076 posts
  • Version:Unknown

Posted 29 May 2012 - 04:46 PM

I agree with the points you have brought up and think any error message done in something you want to sell should be handled in such a way.
  • 0

#8 Pstadler

Pstadler

    GMC Member

  • GMC Member
  • 58 posts

Posted 29 May 2012 - 06:35 PM

Yes, I agree but I think it's the most unprofessionell thing that can happen when an error message comes up to the user.
  • 0

#9 alexandervrs

alexandervrs

    GMC Member

  • GMC Member
  • 423 posts
  • Version:GM:Studio

Posted 07 June 2012 - 03:55 PM

So, what now? I really need the "Show errors" function. And what about the "Thread uninitialized values as zero" function? Thanks!


Added a reminder about this issue http://bugs.yoyogame...iew.php?id=4214 :)
  • 0

#10 vann

vann

    GMC Member

  • GMC Member
  • 356 posts
  • Version:GM:Studio

Posted 01 August 2012 - 01:34 PM

+1, I really think games should not be published with this level of error reporting enabled
  • 0

#11 vann

vann

    GMC Member

  • GMC Member
  • 356 posts
  • Version:GM:Studio

Posted 02 August 2012 - 03:03 AM

alexandervrs, you ticket was closed yesterday with the statement that the error_* functions will not be returning. I've opened a new ticket requesting that debug messages are removed from final builds ASAP, just to ensure that this part of the request can be tracked. Ideally it should still be an optional flag, so you can distribute alphas/betas to trusted parties.

I've made the assertion that this is a release blocker for several users (it is for me), and thus marked it very high, but you may want to add your own comments folks.

You can find it here:
http://bugs.yoyogame...iew.php?id=5769

Edited by vann, 02 August 2012 - 03:04 AM.

  • 0

#12 alexandervrs

alexandervrs

    GMC Member

  • GMC Member
  • 423 posts
  • Version:GM:Studio

Posted 02 August 2012 - 02:49 PM

alexandervrs, you ticket was closed yesterday with the statement that the error_* functions will not be returning. I've opened a new ticket requesting that debug messages are removed from final builds ASAP, just to ensure that this part of the request can be tracked. Ideally it should still be an optional flag, so you can distribute alphas/betas to trusted parties.

I've made the assertion that this is a release blocker for several users (it is for me), and thus marked it very high, but you may want to add your own comments folks.

You can find it here:
http://bugs.yoyogames.com/view.php?id=5769


Okay if I got the reason correct is that final games will not be able to report errors anymore once they are compiled under LLVM. For example uninitialized variables will cause compiler errors and bad code will just crash the game. So final builds apparently won't be able to show any error messages.
  • 0

#13 vann

vann

    GMC Member

  • GMC Member
  • 356 posts
  • Version:GM:Studio

Posted 02 August 2012 - 03:56 PM


alexandervrs, you ticket was closed yesterday with the statement that the error_* functions will not be returning. I've opened a new ticket requesting that debug messages are removed from final builds ASAP, just to ensure that this part of the request can be tracked. Ideally it should still be an optional flag, so you can distribute alphas/betas to trusted parties.

I've made the assertion that this is a release blocker for several users (it is for me), and thus marked it very high, but you may want to add your own comments folks.

You can find it here:
http://bugs.yoyogames.com/view.php?id=5769


Okay if I got the reason correct is that final games will not be able to report errors anymore once they are compiled under LLVM. For example uninitialized variables will cause compiler errors and bad code will just crash the game. So final builds apparently won't be able to show any error messages.


Right, thanks, though I thought final builds were already, you know,. finalised.... :)
  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users