IRC logs for #openttd.dev on OFTC at 2014-05-22
⏴ go to previous day
04:29:27 *** tycoondemon has joined #openttd.dev
05:48:22 *** tycoondemon has joined #openttd.dev
11:16:41 *** tycoondemon2 has joined #openttd.dev
11:32:37 *** Supercheese has joined #openttd.dev
11:32:37 *** ChanServ sets mode: +v Supercheese
12:06:48 *** Klanticus has joined #openttd.dev
12:13:29 *** Klanticus has joined #openttd.dev
15:15:09 *** Klanticus_ has joined #openttd.dev
15:56:19 *** frosch123 has joined #openttd.dev
15:56:19 *** ChanServ sets mode: +v frosch123
16:21:14 *** Alberth has joined #openttd.dev
16:21:14 *** ChanServ sets mode: +v Alberth
18:11:50 *** Klanticus has joined #openttd.dev
18:43:51 *** tycoondemon has joined #openttd.dev
19:14:30 <frosch123> planetmaker: haha, so adf pointed out another issue with the buy+refit patch :p
19:14:39 <frosch123> not only does it not show the capacity, but also the wrong cost :p
19:14:54 <frosch123> and cost is just as impossible to tell as capacity :p
19:16:05 <frosch123> this seems to be the case where it is a single to write a hack, and hundreds to make it correct :p
19:20:45 <frosch123> maybe we should make it a cheat :p
19:21:00 <frosch123> there has been no addition to the cheat menu for long
19:23:40 <frosch123> "enable buggy but useful features" or something
19:24:05 <Alberth> "patchpack features" :)
19:24:42 <Alberth> your 80 idea of the newgrf grfid and md5sum seems to work nicely
19:25:24 <Alberth> should I copy the parameters of the grf when upgrading?
19:26:22 <frosch123> that should be safe if the grfs are marked as compatible
19:26:49 <frosch123> though for telling compatibility you need the version of the grf, which you only have if you still have the old grf file
19:27:06 <frosch123> ah, well, i guess just copy them unconditionally
19:27:48 <Alberth> currently I only upgrade the currently active set, which of course has the grf itself
19:27:51 <frosch123> should be fine in most cases, and not important in the rest
19:28:13 <Alberth> not copying will very soon break
19:28:50 <frosch123> hmm, doesn't it auto-upgrade on loading the cfg when the grf are missing?
19:32:02 <Alberth> maybe the [preset-*] are not loaded, or at least not saved
19:32:27 <frosch123> i think they are only loaded when selecting them in the gui
19:35:15 <Alberth> [newgrf] section is not upgraded, non-findable newgrfs are reported and removed
19:35:42 <Alberth> and since they are loaded and saved, they get the grfid+md5sum
19:36:00 <Alberth> (grfs in the [newgrf] section)
19:36:06 <frosch123> well, it should try to find grfid+md5sum in some other path
19:36:18 <frosch123> and if that also fails, then pick the newest with grfid
19:36:24 <frosch123> and only if that also fails remove it
19:37:51 <Alberth> indeed, if you give a grfid, and a nonsense path, it picks the newest grf
19:39:04 <Alberth> and a good grfid+md5sum and a nonsense path fixes the path
19:40:01 <Alberth> because it picks the correct grf from the big list, and then saves it with its information, instead of using the nonsense path in the cfg file
19:42:05 <Alberth> will see about the compatibility thing
19:42:46 <frosch123> wrt. copying parameters? i don't think that is really necessary
19:43:57 <Alberth> so just assume compatibility :)
19:44:35 <frosch123> the worst that can happen is that is chooses different settings than before
19:44:46 <frosch123> by not copying them that is always the case :p
19:45:19 <frosch123> so, checking compatibility to not copy them means replacing something that works most times with something that works never :p
19:50:45 <Alberth> saving existing presets is also a big PITA
19:51:01 <Alberth> you have to remember the name, and retype it precisely :)
19:51:15 <frosch123> maybe it should not be a dropdown, but a scrollable list?
19:51:36 <Alberth> I was thinking to make it a save-like window
19:51:52 <frosch123> hmm, actually the loading is easier with a dropdown
19:51:56 <Alberth> instead of the current standard one line edit box
19:52:04 <frosch123> maybe the save window should just have a editbox with a dropdown attached
19:52:27 <frosch123> so, not the standard edit window, but with an additional [v]
19:53:07 <Alberth> dropdown easier than a scrollable list?
19:53:34 <Alberth> with loading I can imagine, but saving?
19:53:37 <frosch123> easier to code: likely; easier to use: no idea
19:54:03 <frosch123> loading should use a dropdown since then it can remain the in same window without opening a new one
19:54:09 <frosch123> saving is fine with a new window
19:55:38 <Alberth> ok, enough tonight, see you tomorrow probably
19:56:45 *** Alberth has left #openttd.dev
continue to next day ⏵