So I’ve been working on the code for the Options Menu. I know that the GUI will be changed and so I haven’t focused to much on the small details. However I’ve set up a lot of buttons and some nice features.
Here is the latest video, and picture, which shows the controls section.
Its not hard to code all these buttons, however it can be time consuming as I have to set them all up in the .layout file with XML, them root them in the .lua file, if they are a button I have to set that up as well in the lua as well as their function, lastly I have to make sure they all show/hide when ever a button is pressed. So a lot of copy/paste is being done. But I think it looks nice and gives a feel of a real menu.
It sucks that I can only give you one like. You’ve done a great job with this so far. For the controls, you can easily just modify the controls.lua file (at least I think that’s what it was called) in the root of the scripts directory using simple streams. If you have any other questions just ask.
Used the Symmetry Buttons for +/- would like the minus button to be a real minus.
I didn’t spend a lot of time making the buttons look nice or putting them in the right place as the GUI is going to change soon.
However one thing I would like to do is increase the middle “buttons” and give them a spot to displace the volume level. IE: 100%. However I’m also considering replacing the buttons with a field or label instead.
Oh okay. I still need to set up a variable and how to call the sound first. I have no clue how to do that. And tbh would need someone to walk me through each step.
Could I also get a list of everything that wants to be done for the Options Menu for 0.3.3? There are some things I can do easily and others that require new learning new things. I’d like to be able to get as much done on it as possible, and such was thinking about prioritizing the list.
I’m going to get buttons set up for Music and Sound effects, then we can do sliders for them all. Which I might need help on.
Also what graphics qualities? Be specific as I can get the layout set up first then start coding it all.
With the controls, do you want them to be able to remap the keys? If so would we have to adjust what the tutorial/tooltips say based upon what keymapping is set? I think it could be done, just need some extra variables and some switches (if/if elses)
Yes, definetely languages. I forgot about that. Thanks for reminding me!
For now, the only real graphics thing we have is having the membrane be fluid. We can also increase the spawn radius, which will allow people to zoom out more.
I think we need to have the keys some of the keys be remapped. Others, like print screen, shouldn’t change. And others, like toxin emission, will be edited within the microbe editor. So I’m guessing these ones:
kmp.undo = {“ctrl”, “U”}
kmp.redo = {“ctrl”, “R”}
kmp.remove = {“R”}
kmp.newmicrobe = {“C”}
kmp.togglegrid = {“G”}
Okay sounds good, I was also using the Options -> Controls section to “DISPLAY” all the controls, or would that be somewhere else? Thanks for the reply I’ll try to get the layouts set up this week and we can go forward with that.
With the keymap, since it’s a lua table we can edit the values in the keymap dynamically so they appear immediately in-game. I don’t think it’s a good idea to have scripts edited by the game so you’d have to save the keymap to a save file (plaintext key-value list) much like the other options; maybe make it a separate file so you can have multiple independent control schemes, even.
Okay got the build up on my machine, going to try and redo all this on the new engine.
I have no idea what I’m doing, as well as forget everything about anything to do with coding, so any pointers in the right direction will help me tons!
All the GUI scripts are in thrive/scripts/gui. You need to run cmake .. in the thrive/build folder after changing them to make the game pick up the changes. You can preview the GUI in chrome if you run a web server in the main thrive folder. For example with http-server -c-1 (this is another npm module you can install) and then you can open http://localhost:8080/scripts/gui/thrive_gui.html in chrome to preview the GUI (and use the devtools, and just refresh after making changes for much faster dev cycle).
The formatting script (RunCodeFormatting.rb) also cleans up the HTML, CSS and JavaScript files. You need to have the npm modules installed mentioned in the setup instructions.
Nice work finding the animations.
I think the options button should right away show one of the options categories. We might need a few concept art pieces as to how to layout all the different options to minimize having to click through a bunch of screens.
