On Sun, Feb 19, 2012 at 11:08 AM, Per Inge Mathisen <> wrote:
> On Fri, Feb 17, 2012 at 3:10 AM, buginator <> wrote:
>>> Because we have lots of events being called (and more being added all
>>> the time) that not every script should be forced to implement just to
>>> make the warnings disappear.
>
On Fri, Feb 17, 2012 at 3:10 AM, buginator wrote:
>> Because we have lots of events being called (and more being added all
>> the time) that not every script should be forced to implement just to
>> make the warnings disappear.
>
> Eh ? You are inviting bugs then, as can be seen by 001ef35faf1.
I
On Thu, Feb 16, 2012 at 9:23 AM, Per Inge Mathisen <> wrote:
> A script should not get a warning for every event it does not
> implement. If you want to warn about misnamed timers, this function
> needs an additional bool parameter that is not set for events. If you
> want to warn about misnamed ev
On Thu, Feb 16, 2012 at 2:49 PM, Christian Ohm wrote:
> It looks to me that change adds a warning if we call any undefined
> function. I noticed this behaviour already when I used a wrong function
> name, and it took a bit to find the problem, since the game just
> silently ignored that line. If t
On Thursday, 16 February 2012 at 8:42, Per Inge Mathisen wrote:
> A script should not get a warning for every event it does not
> implement. If you want to warn about misnamed timers, this function
> needs an additional bool parameter that is not set for events. If you
> want to warn about misname
On Thu, Feb 16, 2012 at 4:04 AM, GitHub wrote:
> Commit: b18b76ea8a553b06c4f7258fc8432c7db280b9aa
>
> https://github.com/Warzone2100/warzone2100/commit/b18b76ea8a553b06c4f7258fc8432c7db280b9aa
> Author: vexed
> Date: 2012-02-15 (Wed, 15 Feb 2012)
>
> Changed paths:
> M src/qtscript
