| Age | Commit message (Collapse) | Author |
|---|
|
While testing waters around exporting things out from Game to
GameWinDX9 I noticed that if both ContentBundle and Clock (primarily)
are removed from it, then the WinDX9 will be almost equivalent to base.
This is worrying mainly because I'm only fortified in seeing deep
relationships between various classes sadly including Video.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I don't like having a singleton with inheritance. At all. It needs to
be removed as soon as possible and functionalities need to be moved
outside of this monolith and this is a step into that direction.
I think.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This excludes time compression stuff, as it will need some more
attention due to casting.
I don't quite like the long invocations that go through game instance
first then get the clock. It looks bad. I'll need to rethink how
modules are being made available in the codebase.
|
|
|
|
The interface remains unchanged for now, but changing to use GetClock
or similar method to get clock owned by the Game instance is preferred.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This will allow to split the functionality even further. I predict that at some
point they I will start joining them up together once again, but for now I need
them to be isolated.
|
|
In the long run a more versatile solution is preferred.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It might come back after proper clean-ups and after some of the strong
relationships in the project are gone
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
