https://bugreports.qt.io/browse/QTBUG-51196
https://github.com/jpnurmi/statusbar
- Queries
- All Stories
- Search
- Advanced Search
Advanced Search
Jan 20 2018
Oct 29 2017
Aug 8 2017
Jun 12 2017
Jun 4 2017
May 15 2017
Mar 16 2017
Jan 16 2017
Dec 27 2016
Ah, I see. Will try to report it to Qt soon.
Looks like it should be implemented on the Qt side first, then expose it to the application's QML somehow:
https://github.com/qt/qtbase/tree/dev/src/android/jar/src/org/qtproject/qt5/android
We need C++ as well as most KDE applications will be written in C++.
The following Java code snippet does it.
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP) {
Window window = getWindow(); window.addFlags(WindowManager.LayoutParams.FLAG_DRAWS_SYSTEM_BAR_BACKGROUNDS); window.setStatusBarColor(Color.BLUE);
}
Crash indicate crash in java code (Android code alone) or C++ code as well? I could implement catching crash in Java code and can call DrKonqi.
This task is an earmark that we have to do research about how to best interact with Android's crash log system from a Qt application. Possible outcomes are
- only use the Android crash system, since KCrash does not give an additional gain, or
- going a combined approach, by providing an additional JNI backend to KCrash, or
- something completely different that we did not think about yet.
Hence, there is no straight forward way, but this is a experimental research task where one has to research an assess the different approaches and come up with a viable concept.
I have good understanding of Android, interested in working on this. Would like to know what is the required to be done.
Nov 29 2016
Nov 6 2016
Sep 1 2016
Jul 2 2016
Jun 18 2016
Jun 17 2016
Jun 16 2016
Jun 15 2016
Jun 14 2016
Jun 13 2016
Apr 24 2016
Given that the number of people using the deploy scripts is rather small I'm fine with changing this without much deprecation logic behind. Thanks for taking this on.