⏴ go to previous day
07:29:51  *** adf88 has joined #openttd.dev

07:29:51  *** ChanServ sets mode: +v adf88

08:34:11  *** Supercheese has quit IRC

09:41:48  *** adf88 has quit IRC

09:42:05  *** adf88 has joined #openttd.dev

09:42:05  *** ChanServ sets mode: +v adf88

09:49:07  *** adf88 has quit IRC

09:52:03  *** adf88 has joined #openttd.dev

09:52:03  *** ChanServ sets mode: +v adf88

11:11:33  *** adf88 has quit IRC

14:53:24  *** Ristovski has joined #openttd.dev

15:57:22  *** adf88 has joined #openttd.dev

15:57:22  *** ChanServ sets mode: +v adf88

16:35:21  *** adf88 has quit IRC

17:17:28  *** frosch123 has joined #openttd.dev

17:17:28  *** ChanServ sets mode: +v frosch123

18:36:17  *** Alberth has joined #openttd.dev

18:36:17  *** ChanServ sets mode: +v Alberth

18:45:11  *** DorpsGek changes topic to "OpenTTD Dev Channel || Latest SVN: r26287 || Logs: http://webster.openttdcoop.org/?channel=openttd.dev || Voice (talk-right) upon request via #openttd; make sure you are registered to NickServ before asking"

19:04:49  *** adf88 has joined #openttd.dev

19:04:49  *** ChanServ sets mode: +v adf88

20:16:50  <frosch123> hmm, should vehicle var 61 set "available = false" when used in disallowed callbacks instead of returning 0 ?

20:20:17  * Alberth hopes you're not asking me :)

20:21:44  <Alberth> ...If the offset is outside the vehicle chain, the result value will be 0.  <-- isn't it doing that already?

20:22:51  <frosch123> "It is not supported during a callback that is used to modify vehicle properties to avoid circular dependencies, which currently limits this variable to callbacks 1D, 2D, 31 and 32 plus outside callback scope." <- i am refering to that case of invalid grf

20:24:49  * Alberth nods

20:25:38  <Alberth> apparently "not a valid offset" is different from "available = false" for you

20:27:58  <frosch123> well, the point is, returning zero is not the same as returning "not available"

20:28:12  <Alberth> I understand that now :)

20:28:32  <frosch123> "not available" results in debug output and a throw-like special grf behaiour

20:28:35  <Alberth> and yes, it makes sense to say "we don't have that callback in those cases, I think"

20:29:00  <Alberth> s/, I think"/", I think/

20:44:47  <planetmaker> frosch123, how would a newgrf behaviour change (from user perspective) if it currently uses it?

20:45:37  <frosch123> "not available" means aborting the current switch (skipping register assignments and such), and immediately continue with the default case

20:46:28  <planetmaker> ah. yes, sounds reasonable then

20:46:29  <frosch123> it's a weird thing, but the positive aspect would be that https://bugs.openttd.org/task/5848/getfile/9637/fs5848trace.png could list it as bug

21:01:35  *** Supercheese has joined #openttd.dev

21:01:35  *** ChanServ sets mode: +v Supercheese

21:22:24  *** frosch123 has quit IRC

22:00:08  *** Alberth has left #openttd.dev

22:00:20  *** Ristovski has quit IRC

23:26:28  *** Supercheese has quit IRC

23:38:52  *** adf88 has quit IRC

continue to next day ⏵