.. by not executing duplicated checks and not using the common lib for now (needs to be aligned if possible)
Signed-off-by: Marcel Hibbe <dev@mhibbe.de>
= Change navigationBarStyle to SystemBarStyle.light
This is done to align with the XML screens, see comment.
Signed-off-by: Marcel Hibbe <dev@mhibbe.de>
color statusbar for composable screens by adding a colored Box where the statusBar is (or fallback to coloring via window.statusBarColor)
Signed-off-by: Marcel Hibbe <dev@mhibbe.de>
E.g. for older server versions
Without this fix there would be the crash:
E FATAL EXCEPTION: main
Process: com.nextcloud.talk2, PID: 7161
retrofit2.HttpException: HTTP 405
at retrofit2.KotlinExtensions$await$2$2.onResponse(KotlinExtensions.kt:53)
at retrofit2.OkHttpCall$1.onResponse(OkHttpCall.java:164)
at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at java.lang.Thread.run(Thread.java:1012)
Suppressed: kotlinx.coroutines.internal.DiagnosticCoroutineContextException: [StandaloneCoroutine{Cancelling}@4a67b41, Dispatchers.Main.immediate]
Signed-off-by: Marcel Hibbe <dev@mhibbe.de>
1. reverting changes from commit 971cc79b76. The scroll to methods are used in other places and a user reported that the search window suddenly opened without to search.
2. remove checkIfMessageIsSaved method. If the message is saved or not does not matter. The only fact for "scroll to" would be that it's loaded in the adapter.
3. As the adapter is always null with the current implementation (when coming back from the first search window), the "scroll to" is replaced with the startContextChatWindowForMessage. This could be changed again when adapter is not null anymore after coming back from the other screen...
startContextChatWindowForMessage
Signed-off-by: Marcel Hibbe <dev@mhibbe.de>
There was a report that the app crashed after coming back from PIP mode.
And i once saw in logs
"call to OpenGL ES API with no current context (logged once per thread)"
By initializing rootEglBase very early there is a chance this fixes these issues.
Signed-off-by: Marcel Hibbe <dev@mhibbe.de>
not sure why "Property name should start with a lowercase letter and use camel case (cannot be auto-corrected)" is shown.
also see commit
523b8080d1
Signed-off-by: Marcel Hibbe <dev@mhibbe.de>
