Irrelevant Pixel
  • Introduction / Foreword
  • ↘️Integrating Menu into your game
    • Add to your project
    • Maps and Modes
    • Your Game Instance
    • Play in your Level
    • Turn ON Enhanced Input
    • Mouse functionality
    • Integration completed
  • Getting to know how to use it
    • Creating Page for Options
    • Selector
    • Slider
    • Toggle
    • Keybinder
      • Duplicating Keys
    • Stylizing Interactive Widgets
    • Save your Options
    • End of the Basic Usage Manual
  • Advancing into Internal Structure
    • Core Concepts
    • Page-related things
    • Aspect Ratios + Resolutions
    • Graphics 'Overall Quality'
    • Deeper into (C)Stylizing
    • deleting Dev.Tool
Powered by GitBook
On this page
  1. Advancing into Internal Structure

Deeper into (C)Stylizing

Here I mentioning few more important things about Common Styling

Last updated 9 months ago

Common Styling functionality is intended to cover only the most complicated stuff - interactive widgets, which are all consist of different kinds of parts and widgets. Some are Buttons, Combo Box, Progress Bar, Images, or whoever knows what else it might be. Once desired, it is all supposed to be changed simultaneously and maintain the same appearance.

The Styling of all other widgets in this Menu is not handled like that, those are kept raw, and since they are very primitive and simple, it could be easily expanded.

Some precautions if going with non-common styling

Most of the four Modular Options on their Pre-Construct / Construct has two parts that are responsible for Common Styling:

Initially all of that was just in once place - Resolve Common Styling, but then it was decided that it is better to split for sake of safety.

Compare now those two variations of how it could be done.

  • first one is using the function from the actual Widget

  • second is using from the completely separated variable(copy of the Widget's Style)

The issue is that this Set Members function takes some Ref as the source and then overrides desired things in it. If you use such a function from your Widget directly - it will override whatever you had in your Editor's Slate, and once you want to turn off Use Common Styling, you'll realize that all your previous progress is gone and replaced with those things from the blueprint.

It is actually quite easy to introduce new elements (or disconnect existed). Just open a few Modular Options and take a look inside the Graph and see how existing Styling is applied in those blueprints.