-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improvements to OptionsMenu.wnd
#2567
base: main
Are you sure you want to change the base?
Conversation
I have adjusted the positions of all controls to use consistent and logical values based on the 800x600 resolution. This ensures a more structured and organized layout, making the interface easier to maintain and visually cohesive. For example, vertical spacing between controls in sub-windows is now consistent (e.g. to a fixed value of Below is a preview showcasing the updated layout: |
Update
Also, I noticed the following control: Advanced Display Settings winBefore:After: |
Nice effort. Correcting the positioning is very nice. This pull is still marked as draft, but here are some notes: Options menu:
(*1)
Advanced Options menu:
ConsiderationTo create Control Bar Pro, we used mockup images to draft the layouts. This helped a lot to create consistent visuals across window elements. 3-4 years ago I did draft a few Menu mockups, but never continued that effort. Perhaps it would be worthwhile to draft mockups for all game screens. It can help to achieve truly consistent layouts and styles. But it needs to be catered to specific aspect ratio. Control Bar Pro catered to 16:9 (1920x1080). Original game caters to 800x600, which obviously is severely outdated, but we need to support this to preserve original capabilities. I can upload these mockups if you are interested. It does not need to go into this direction, but it possibly can - if it is good. |
Please prefer uploading JPG over PNG for complex images like this. PNG is good for images with simple shapes. JPG is better for complex images. Answers to questions:
I do not understand. Can you give examples?
I suggest to test if they do anything. If they do nothing, leave them hidden. If they do something useful, can show them.
As far as I know it is not possible to add comments to WND. It is a generated format that has strict syntax and no comments. We can however add comments if we strip them out before build with Mod Builder. We currently do not do this, but it should be possible. It would require a change in ModBundleCoreItems.json, adding a |
Thank you for the valuable feedback! I really appreciate the suggestions, and it’s precisely why I marked this pull request as a draft—to get input and better understand the community’s direction before submitting a finalized proposal. Feedback Notes and My Responses:
This was a design choice for the headers, but I will revert it for consistency.
Fixed.
I propose moving the
Done and fixed.
I'd appreciate guidance on how to implement this consistently. Currently, there is a
Fixed.
The shorter sliders are intentional. Following point 4, I divided the display into two sections, ensuring the sliders start and end in the center of their section. The text is also centered within its respective section.
Same :). Additionally, I'd like to mention that determining positions and reducing empty spaces is challenging because the text length in different languages must be taken into account.
I’d love to see the mockups; they might inspire further improvements.
For instance, sliders like FX and Music are located outside the container for AUDIO. Also, I’ve been using WNDEdit to make editing these files more efficient and precise. One question: Is there a community-agreed palette of colors and their corresponding codes? I’d like to apply a consistent palette across menus if possible. Thank you again for the guidance and support! 🙏 |
Issue: ComboBox Menu Exceeds Main Container Bounds is Not Working
EDIT: The issue was fixed by limiting the dropdown to only 2 items, keeping it within the bounds of the main container, using a scroll bar. |
To me it looked better before, because the items aligned with the audio items.
We cannot change the capabilities before Thyme is ready. My suggestion simply is to not enable the CENTERED titles yet, because it would require to center all titles for consistent look. But this change only caters to Options Menu. So my suggestion is to hold off with CENTERED:1 until it can be done on all windows if we so desire. (Having it in a single change also makes it easier to revert in git)
Yes, but is this necessary? To me it looks like there is total freedom in length.
Yes. Empty space is ok, I just thought I mention it for consideration.
Menu mockup samples here: Full Control Bar Pro mockups here:
The sliders are in AUDIO OPTIONS.
Personally I have not been using WNDEdit for any WND edits, because it does not work with some of the files and seems impossible for the ControlBar.wnd.
I briefly looked at menu colors with #686 (comment) but have not driven it to any results. What we have done for Control Bar Pro faction colors is creating color palettes with the existing reference material like outlined in this tutorial: The color palettes were then added to: And this is what we mostly used. For history on Control Bar redesign effort you can look at this topic: Significant effort was spend with mockups and designs to figure out where we want to go before actually committing to it. |
A proposal for a new layout of the options menu to include additional controls, such as camera controls #2569 (comment). The window is shorter in length, so you can extend it and add more few controls if needed. |
It is a decent direction. Perhaps elements are a little bit too cramped. I think it would be good to design the GUI with element spacings that are consistent across all windows. Perhaps the 4 sub sections in the OPTIONS menu could be sized with identical dimensions - if they contain about the same amount of elements. |
Version 3 Update:Here is the layout after adding the additional controls. Issues:
Questions:
800x6001080x1920 |
Okay, I saw your YouTube video and realized I wasn't clear, I mean the wnd file itself Here is an example of how the file should be organized for a window and controls in the window (children of the main window)
Here is an example of how it is in practice, you can see that a control that should be inside a window appears outside its block, and is now not a child of it but a sibling.
In our case, the FX and Music sliders do not appear in their correct place in the code lines, but later in the file. They are not 'children' of the audio window, but of the main menu. Is it possible to reorganize the lines of code? Also, delete irrelevant lines, for example, there is duplicate code for the main menu background and two backgrounds are actually loaded, you can see an example below. I also found that comments using ; are not problematic. Here's how the hierarchy looks now and how it should be: |
Pull Request: Improvements to
OptionsMenu.wnd
Summary
This PR introduces initial improvements to the
OptionsMenu.wnd
file, focusing on symmetry and visual organization of UI elements. The goal is to enhance the layout and readability. Future work may include improving the color scheme for better aesthetics.Questions and Considerations
1. Reorganizing the File Structure
I noticed that some controls are not aligned with their expected hierarchy in the file (e.g., not grouped under their logical containers).
2. Unused or Hidden Controls
There are controls in the file that do not seem to be visible in the UI or linked to any current functionality. Examples include:
(Edit: A separate issue has now been opened for this topic #2569 )
3. Documentation
Would it be acceptable to add comments or documentation within the file for better maintainability? This could help future contributors understand the purpose and functionality of each control.
Before and After (getting updated)
Main Options win
Before:
After: