Preferences screen once more

By

I thought that the preferences screen is all done, but then I noticed there are still some things missing, like confirmation dialog on "Quit" button, audio preview when changing speech/sfx volume and more.

When I was proofreading the previous entry I noticed the typo in bootstrapping class, it was named as BootsrapManager (missing "t") so I've renamed it to BootstrapManager. Well, it is funny that I didn't find it earlier, but with autocomplete in IDE you don't check typos.

The next thing I was working on was message dialog. But as first, the support for 9-slice sprite was needed. Therefore, new import type was defined in StciImporter which will take the sprites from the .sti file and create the one 9-sliced sprite from it (it is actually 8-slice sprite, as the "content" is transparent, because each dialog could have its own background image).

Message dialogs are implemented using solo canvas, with stacking dialog supported. Each dialog prefab contains the "blocker" part (so no UI beneath it could be interacted with) and the actual dialog. There is an DialogManager which is responsible for the dialog creation and destruction and then a MessageDialogComponent, which does handle the dialog interactions. For now only "OK", "YES"and "NO" buttons are supported.

Quit dialog message 


 

Another thing thas was rewritten was that game settings option numeric values are now stored in the "natural" range and not in <0,1>. Also, default value is in <min,max> range now. The conversion to <0,1> range happens only when needed, mostly for the UI elements.

There was another change regarding the options and that is option groups. This is used for situation, when at least 1 of the 2 option must be selected (like "Speech" or "Subtitles" should be on). This is defined in AssetGameSettingsData class, where multiple option groups could be defined. Then, in preferences screen, the check is done and if situation like the above happens, message dialog is shown.

Option groups in action

Then the "quit" dialog command was implemented, with showing the message dialog and quitting back to the main menu, if confirmed.

The last thing that has been done is audio preview when changing the sfx/speech sliders. The actual preview is done in ViewModel, using newly created AudioPreviewService. And also, when the option in the list view is checked, audio effect is played for the check/uncheck event. At first, I was using Toggle's event changed but that was problematic, because this event fires in various places, not only when the user clicks the Toggle. Therefor new event was added in Toggle4State class, which is raised ONLY on "external" clicks (For more info see https://github.com/VPDPersonal/Aspid.MVVM/discussions/275).

There was again, as always, various bug fixes, like hard-coded enum values for AssetType enum, fix of toggle rendering in options list, button disable state rendering and more.

Comments

Post a Comment

Popular posts from this blog

Main menu updates

By
Image
W ell, another "long time no see". I'm still working on the project as much as I can. But it's not a steady work. During summer I was doing some other things (like bike touring) and mostly work. So, what's new? Well the main menu is working. While working on it the need arise for some sort of "mockups" components for various asset and mockup manager. Let me explain why. Because the assets of JA2 are proprietary, it means that you need to extract and build the asset bundles by yourself. Therefor all the assets in the GameObjects needs to be referenced indirectly (because they may not exist yet). This is where mockup come on scene. The mockups are just references to the real assets (like pointers in C++). And when the scene is loaded, the mockup manager primary role is to load the real assets from the mockups. Also, the main menu is implemented using Aspid.MVVM package (MIT licensed). Some other minor changes is custom Script edImporter for .pcx and .st...
Read more

Project reborn

By
W ell, after a long time of inactivity I started to work on this project again. It's been a long time since I touched the project. I've got a lot of other work to do, and also other "spare time" projects to work on. This time, I'll be using Unity engine. So, the basic infrastructure is almost done. At moment I'm working on the UI stuff. The project would be using uGUI (Unity GUI) with some MVVM library. The one big difference from the previous project is, that original JA2 data would be needed only in build time, not in a runtime. There would be editor utils, that will convert the original JA2 data to the format Unity could work with. This means, that every user would need to do this step manually as I don't think it would be legal to distribute it. After the working main menu I would post a github link to the project as I need to also update readme.md so anyone would know where to start.
Read more

Changes to string handling - UTF-8

By Siver. T
So after some time here are some minor updates on project. As first, std::wstring was replaced by std::string (as UTF-8 as default) as it somehow wrong approach to use std::wstring anywhere. For more details see [1], [2], [3]. All std::string now by default hold UTF-8 valid string. As next I will change all projects to use unicode by default and use wide WinApi functions (with help of core::ConvertClass). As second some changes were made in whole game state/screen/handling management. There was added some new classes for init screen handling and so. As usual you could see changes in google code project site. For the near future I'm planning to implement MouseRegion class and the go to GameManager::run(). And happy new year :) [1] - boost.devel thread about strings, UTF-8, ... [2] - boost.devel tread about strings and future [3] - stackoverflow question about UTF-16
Read more