Added a Keyboard Controlled Focus Indicator

[andystopia]

Motivation

Keyboard control.

If you don't recognize a class name, that's because I wrote it.

Change Log

• Move all GameManager implementation details into delegate classes. Game Manager should only delegate information about other classes, not implement anything itself.
• Have a TileManager
• Delegate creation of tiles from the tile manager to a TileGrid. This isn't a complete delegation as they codepend on each other, and also TileGrid is not the most base class it could be. It very much should have an inheritance tree, so that we can more easily work on efficient implementations, but this is good enough for now.
• I'm not sure whether the FocusIndicator is in the repo yet or not. If it isn't then, that's fine, this one will add one and basically all it does is controls and animates for rectangles to draw a different rectangle with a certain color. Definitely limited in a lot of ways such as not being able to use AnimationCurve and not properly delegating it's functionality which is a violation of SRP. Like I said though, I just want to allow other people to
• Added a few helper classes which can calculate the bounds of GameObject trees, proper modulus and ensuring a component is the only component to implement an interface.
• Wrote a circular array implementation for structures that don't really have a concrete need for a start and an end.
• Delegation of tasks, reduction of work of basically every class I modified.
• Added IGridPosition, for location of items on a grid.

  Now for the hard part.

Basically my design philosophy is that there is a lot of state in this game. Those states can be divided into two separate concepts. Inclusive States and Exclusive States. Exclusive states are states which are mutually exclusive from all other states. Inclusive states are the states of co-existing states. All of this program is an exclusive state, although it certainly does not need to be that way.

So for most objects, there will be several components. There will be a selection component (BlahBlahBlahSelectionInteractor) inside the object, and there will be a selection manager, outside the object. Right now all the managers are exclusive, although that could certainly change in the future.

There is also focus components, and these are a little more complicated. These tie a bunch of things together. You'll have the same FocusInteractor (on the object), and FocusManager outside the object, except FocusManager is itself managed by ActiveRegionFocus, which ensures only one focus manager can be focused at any given time (exclusive state).

This is because something could be focused (like when it's hovered), but not selected( like when it's clicked)

Each focus interactor will also have several dependencies as components:

• A FocusDisplay, with an IBlahBlahBlahFocusDisplay interface.
• Each FocusDisplay I wrote utilizes the FocusIndicator (that rectangle thingy), but it certainly doesn't need to at all times, it's just my way of denotation).
• Since each FocusDisplay references the FocusIndicator it needs a way to get the bounds defined by (IFocusable), so it generally will utilize some base class of RendererBoundsFocusable. I just slapped everything with the inherited class RecursiveRendererBoundsFocusable (which is expensive, but easy to use).

I also wrote an observer pattern for events, but it seems to me as though this is a bad plan, and it looks like most people use a ScriptableObject Observer pattern instead, which, admittedly, is a much better idea, but still probably a little hard to use. So I don't actually use the observer's I wrote, but I just didn't feel like deleting them.

Please use this system or propose an alternative; state desync is really hard to deal with.

Bugs

Due to the desync of TileSelectionInteractor and TileFocusInteractor, sometimes mouse events cause the FocusIndicator to be black, this is a bug that needs to be fixed, but not one that I cared fix before publishing.

The renderer bounds of objects cannot be known until they render, so you can't set a focused object on the first frame accurately, because it will just give you an all zero bounds. Not really sure how to fix this one, maybe we can defer for a frame? We could open an issue to discuss this one.

Due to the fact that tiles with turrets on them can't be clicked when a turret sits on top of them, I removed that collider on turret, so turrets can no longer be disabled by mobs thanks to the fact that it uses a Physics collider to calculate.

Details

You may notice the TurretShopSelectionManager isn't used, that's because I use the OldTurretShopManager, since they implement the same interface, which allows the bottom left turrets to highlight when I select using my custom menu.

Keyboard Controls are as follows:

• WASD
• X and Enter are your activator keys
• Z pulls up the turret shop.

[andystopia]

I closed my other one, and it can be deleted, because when I merged it with my own main branch, it had a flaw with the range indicator not disappearing, so I merged into my main branch, tested, and am now submitting it.