IRC logs for #openttd.dev on OFTC at 2014-04-26
⏴ go to previous day
06:13:50 *** Hirundo_ has joined #openttd.dev
06:14:00 *** TheIJ` has joined #openttd.dev
06:22:58 *** Alberth has joined #openttd.dev
06:22:58 *** ChanServ sets mode: +v Alberth
09:49:55 *** frosch123 has joined #openttd.dev
09:49:55 *** ChanServ sets mode: +v frosch123
11:10:15 *** Alberth has left #openttd.dev
11:32:29 *** Supercheese has joined #openttd.dev
11:32:29 *** ChanServ sets mode: +v Supercheese
13:41:28 *** tycoondemon has joined #openttd.dev
15:27:23 <fonsinchen> Ignore the second one for now :/
15:57:37 <frosch123> maybe add the unit of the values to the doxygen comments of the get/set methods
15:57:48 <frosch123> ticks and km-ish/h i guess
16:11:54 *** Alberth has joined #openttd.dev
16:11:54 *** ChanServ sets mode: +v Alberth
19:33:50 *** Alberth has left #openttd.dev
19:41:37 <frosch123> mostly removing "auto" when there is nothing auto-ish
19:42:36 <Supercheese> It will help some of my translation woes as well
19:43:53 <fonsinchen> The fact that auto-refit and auto-refit aren't the same has been bothering me for a while.
20:10:47 <fonsinchen> relevant features are "better estimates for link capacity" and "instantly autofill timetable"
20:15:07 <frosch123> b8b4: ChangeTimetable lacks @param
20:17:46 <Rubidium> the github diff thingy sucks as I can't see the end of many lines
20:18:05 <frosch123> keyboard scrolling works :)
20:18:16 <fonsinchen> append a ".diff" to the end of the url for the raw diff
20:19:51 <frosch123> does the autofill timetable still work when only some orders already know their duration?
20:20:16 <frosch123> hmm, didn't it even used to delete all times?
20:20:48 *** andythenorth has joined #openttd.dev
20:20:48 *** ChanServ sets mode: +v andythenorth
20:21:01 *** andythenorth has left #openttd.dev
20:21:07 <fonsinchen> The chosen vehicle will still start its autofill loop
20:21:19 <fonsinchen> So, the times can still be updated if they're missing.
20:21:42 <fonsinchen> It's just recycling some already known times to potentially shorten that process.
20:22:03 <frosch123> hmm, what does this exactly do?
20:22:17 <frosch123> it records times for order even when timetabling is not used
20:22:36 <fonsinchen> Yes, but it flags them as "inactive for timetable".
20:22:51 <frosch123> are these times updated constantly? resp. are they no longer updated when timetabling is used?
20:22:51 <fonsinchen> That's what those different GetXYTime methods are for.
20:23:16 <fonsinchen> They aren't updated if they are flagged as active for timetable
20:23:26 <fonsinchen> (and if not autofilling)
20:24:05 <fonsinchen> Otherwise they are constantly updated.
20:24:06 <frosch123> ok, so enabling timetable is now something like "freeze current times"
20:25:32 <Rubidium> I'm missing savegame conversion (setting/clearing the bit)
20:26:58 <frosch123> is there a reason why the methods use "uint8 mode" instead of "UpdateMode mode" ?
20:27:29 <fonsinchen> It's a field of flags, you can set multiple of them
20:27:47 <frosch123> DECLARE_ENUM_BITSET ?
20:28:02 <frosch123> DECLARE_ENUM_AS_BIT_SET actually
20:28:38 <fonsinchen> Interesting, didn't know that one.
21:07:04 <fonsinchen> I've fixed the saveload, UpdateMode, and ChangeTimetable-param things.
continue to next day ⏵