Posted: Mon Jan 02, 2006 3:02 pm
> Beware! Although it might not be a bug, using "Set ... to CE Delay"
> multiplies CE Delay with 50 if it's set to seconds and not frames. This is
> due to the fact that 1 second = 50 frames. - Just took me some time to
> figure out why it was like that...
Ouch!! :-o
No, it was not supposed to be like that. As those parameters which can be set to "CE delay" are not necessarily delay values (score, CE score, CE value, ...), setting them to "CE delay" should only set them to the numerical value in that counter gadget, but not to the internal representation (which is identical to the counter gadget value for "frames", but multiplied with 50 for "seconds", as 1 second == 50 game frames, as Zomis already mentioned). Using the internal delay value would be really confusing, so I just fixed it to let "CE delay" just refer to the value as given by the counter gadget.
More on the rest of the bug report later...
> multiplies CE Delay with 50 if it's set to seconds and not frames. This is
> due to the fact that 1 second = 50 frames. - Just took me some time to
> figure out why it was like that...
Ouch!! :-o
No, it was not supposed to be like that. As those parameters which can be set to "CE delay" are not necessarily delay values (score, CE score, CE value, ...), setting them to "CE delay" should only set them to the numerical value in that counter gadget, but not to the internal representation (which is identical to the counter gadget value for "frames", but multiplied with 50 for "seconds", as 1 second == 50 game frames, as Zomis already mentioned). Using the internal delay value would be really confusing, so I just fixed it to let "CE delay" just refer to the value as given by the counter gadget.
More on the rest of the bug report later...