Does anyone know why TApplication.HintShortPause is 0 by default (in XE and newer) although documentation says it's 50 to avoid flicker (which I have because it's 0)?
Look at the source code, it clearly states why it's 0 and what it's value was before. Who needs revision control if you can keep the old stuff as a comment. ;)
Yes, the comment says "default reshow pause to 0, was DefHintPause div 10". And the documentation states that it should be 50 to avoid flickering. So I suggest someone was out of his mind when he changed that (and also forget to tell the documentation guy, right?) Otherwise there might also be a good reason that got changed but I don't know it.
just to get your attention? ;)
ReplyDeleteThe guy at Emba: "I wonder what happens if i changes this..."
ReplyDeleteLook at the source code, it clearly states why it's 0 and what it's value was before. Who needs revision control if you can keep the old stuff as a comment.
ReplyDelete;)
Yes, the comment says "default reshow pause to 0, was DefHintPause div 10". And the documentation states that it should be 50 to avoid flickering. So I suggest someone was out of his mind when he changed that (and also forget to tell the documentation guy, right?) Otherwise there might also be a good reason that got changed but I don't know it.
ReplyDeleteAnother example of a bad code comment. If there was a reason, one should comment on that. Not the previous value and how it was calculated.
ReplyDelete