OLives Dev Blog

– Move some enums from the Object class and ObjectManager to globally accessible places
– Do not draw the currently selected model in shop mode
– Move the bulk of the game world to graphics coordinates calculation from the object manager to the model manager to make it accessible from other parts of the code

This commit contains preparatory work for the “have a preview of what you are about to place” feature which will be active when placing (read: buying) new objects or move existing ones in the shop mode.
The most important change here is to move the model position/rotation/elevation calculation code out of the object manager to a more accessible and less dependency-ridden spot in the model manager.

Add a maximum padding setting to the DynamicRowContainer

This adds the concept of maximum padding in-between child elements to the DynamicRowContainer. By default the container tries to calculate a dynamic (x axis) padding so that the elements use all the available space.
Under some circumstances, that can look more than a little awkward though:

This can be remedied with the new maximum padding, if set it will use the value as maximum distance in-between elements, everything below that threshold will still get calculated dynamically. In order to see the difference check out the same situation with the new setting:

…which looks arguably better.

– fix logic in pagination row calculation
– fix pagination button logic
– improve state hash calculation function on the status bar
– replace the RowContainer instance used as the context container with the DynamicRowContainer

This finishes up the DynamicRowContainer for now. Some tweaks had to be made when determining the limits of how far the user gets to paginate/scroll and what state the scroll buttons need to be in accordingly.
If the number of child element now exceeds what can fit in a row, the buttons are shown properly now:

Finally the container type was made to replace the existing “context container”, which is the internal name for the big area on the right in the UI next to the main UI elements on the left hand side which are always shown.
In order to make this fully work some smaller changes also had to be made in the way that the container sets the sizes of its child elements and thus might implicitly change their dirty state. In other words: the elements might not update properly under some circumstances.
See it in action in the shop mode:

– improve child positioning (still WiP for the reduced padding version)
– add pagination buttons if necessary
– preliminary pagination mechanics (not quite working)
– add some default textures on the texture manager so that widgets can show certain basic textures without a need to have a texture manager instance

This adds the bulk of the mechanics for the pagination, this still requires some tweaks though. That means it will already show the pagination buttons if need be, otherwise it will use the full width to show the actual content.
The other change made is that the TextureManager now always pre-loads some basic UI textures, amongst those the scroll up/down textures and also exposes these texture IDs publicly, so that they can be used from anywhere without having an instance of the TextureManager ready.

Start fleshing out the positioning of elements in the dynamic row container

This adds a first semi-working version of the element positioning/sizing code. While the pagination code is already present under the hood, it is not yet exposed via buttons.

Add the skeleton and first bits of implementation for a semi-dynamic container widget

This introduces the beginning an partial implementation of the DynamicRowContainer. Unlike the regular RowContainer class this will support a dynamic (hence the name) number of elements and pagination.
However, unlike the RowContainer (or ColumnContainer) it will only allow the child elements to have a specific size and ratio. The size is calculated based on the desired number of rows and the number of elements per row as well as an aspect ratio.