sghpjuikit
commented
6 years ago I have experienced this problem before and it is related to the initialization dependecy order. In short guide requires application to be initialized, but something causes guide to initialize before application is done with its own initialization and thus the Guide gets a nullpointer because APP field is null.
The stacktrace is hidden so I can not tell what the problem is from your post, but as a tmp workaround, try
- in APP.class
@F val guide = Guide(actionStream)->@F val guide by lazy { Guide(actionStream) }
if that does not work
- remove line 86 in Guide.class. Its the line that accesses APP field
The ultimate solution would use one of 2 approaches
- signal application start event to the guide differently - pass the event bus to the guide through constructor. I dont like this approach as it is very arbitrary.
- pass App instance (this) to the guide through its constructor. I dont like this approach, because App is basically a service locator and should normally be fine to be an implicit (hidden) dependency - not go through the constructor. It does opens us to problem such as this.
An alternative solution is to initialize the static APP field right at the beginning - before any field from App initializes. I came up with this solution: ` // this is 1st field in the App.class private val initializationInvoker = singletonInitializate()
fun singletonInitializate() {
AppUtil.APP = this.takeIf { AppUtil.APP==null } ?: fail("Multiple application instances disallowed")
}
init {
/// this block no longer initializes the singleton APP field
}`
Pls report if the last solution works and what you think about the proposed solutions.
xeruf
I can't start the player right now from the main branch :/