
I hereby license the file gui1.png under the CC-BY license
I hereby license the file gui2.png under the CC-BY license
I hereby license the file gui3.png under the CC-BY license
> Attachment: gui1.png - color choice feature (267k)
I actually wanted to have a moving Clonk in the color picker, but it's not trivial because that means we'd have to load Objects.ocd.
> Attachment: gui3.png - resolutions option (347k)
Yeah that checkbox is probably obsolete now and should be removed.

>it's not trivial because that means we'd have to load Objects.ocd.
Why not hard code it?
> I actually wanted to have a moving Clonk in the color picker, but it's not trivial because that means we'd have to load Objects.ocd.
Why would you need to load the full Objects.ocd? Can't you just read Objects.ocd\Clonk.ocd\Graphics.mesh with C4Group?


Another thing that doesn't have a simple and beautiful solution. One could send all available Titles with the network reference, but that would defeat language packs. One could load the titles for locally available scenarios, (on occasion, one would probably also load the icon) but that's dangerous in regard to blocks and loading times and can't work for unavailable scenarios.

>One could send all available Titles with the network reference, but that would defeat language packs.
What do titles have to do with language packs? Locally they are already "replacing" language packs? So why not just send them over the internet, just like the scenario goal.

>One could send all available Titles with the network reference, but that would defeat language packs.
What? Language packs have never been asynchronous anyway, have they? Afaik you have to have the same scenario with the same Language*.txts, so if you haven't got the language pack you haven't got the scenario, so any local lookup-solution won't help either.
>One could load the titles for locally available scenario
You don't need to sync that stuff up. As you mentioned first, you simply send them all by adding TitleDE=, TitleUS= etc. to the reference for the masterserver. That usually only includes english and german anyway, which can't hurt that much amount-wise especially when seeing what other kinds of non-important stuff are transmitted.
Well, what do we do if, say, a french person looks at the reference of somebody that doesn't have a french language pack installed? And even if the host had it installed - do we really want to speculatively load all language packs just for the scenario titles?
Not saying that this is impossible or anything, just a bit awkward. I still think the best solution would be to fallback to the Scenario.txt Title. If the author's half-way considerate, that will be a title that's internationally understood. Good coding project for somebody looking for something easy.
Not saying that this is impossible or anything, just a bit awkward. I still think the best solution would be to fallback to the Scenario.txt Title. If the author's half-way considerate, that will be a title that's internationally understood. Good coding project for somebody looking for something easy.

Also, the buildings should have icons that carry information about the structure's function and are distinguishable from the menu background.
Im talking a heated metal ingot icon for the foundry, a hammer hammering on a hammer for the tools workshop, a lightbulb for the inventors lab, stuff like that.
Im talking a heated metal ingot icon for the foundry, a hammer hammering on a hammer for the tools workshop, a lightbulb for the inventors lab, stuff like that.

I find myself looking through the whole hammer menu to find what I wanted to build more than you might expect.

Problem is we'd probably need it for *all* buildings for consistency.

I hereby license the file numbers.png under the CC-BY license


Also I addressed the possibility of multiple choices.
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill