SciChart® the market leader in Fast WPF Charts, WPF 3D Charts, and now iOS Charting & Android Chart Components
We also have a tag=SciChart on Stackoverflow.com where you can earn rep for your questions!
Tell me please why this is happening (in logcat) This is the message I always get the first call or load the markup with scichart
03-30 14:20:46.406 3564-3564/com.gtmobile D/WellDetailChartFragment: BEFORE INFLATE…
03-30 14:20:46.457 3564-3564/com.gtmobile E/libEGL: call to OpenGL ES API with no current context (logged once per thread)
03-30 14:20:46.471 3564-3564/com.gtmobile D/WellDetailChartFragment: AFTER INFLATE…
Сan anyone give me an example of markup for <android.support.design.widget.CoordinatorLayout>
what should I use there is a container to display the scichart?
Have tried containers for Fragment with scichart :
in the first case gives an error (Perhaps this is not acceptable, because the container has a scroll)
<android.support.v4.widget.NestedScrollView android:id="@+id/well_detail_container" android:layout_width="match_parent" android:layout_height="match_parent" app:layout_behavior="@string/appbar_scrolling_view_behavior"/>
in the second case is not displayed, ie just empty.
<FrameLayout android:id="@+id/well_detail_container" android:layout_width="match_parent" android:layout_height="match_parent" app:layout_behavior="@string/appbar_scrolling_view_behavior"/>
I need to work in the wide screen mode (tablet) has several elements on the screen.
In simple activity (as in your examples) everything works perfectly.
On my test device Android 7.0
Android Studio 3.1
I am using trial version scichart which will end in a few days 🙁
Thanks in advance for any information.
Thanks for your inquiry.
I’m not sure that there is something we can do to fix this message because this message is device specific ( couldn’t be reproduced on all type of devices). May I ask which device do you use for testing? Does it support OpenGL ES 2.0? I’ve tried to reproduce it on Samsung Galaxy S3 with API 19 and I don’t see it. I’m asking because this message could be caused by some bug in OpenGL driver for your specific device or custom Android firmware created by device vendor.
The only workaround in this case which should prevent showing of this message is to switch on other RenderSurface implementation which doesn’t use OpenGL for drawing:
// use alternative RenderSurface implementation which uses Canvas API for drawing surface.setRenderSurface(new RenderSurface(context));
Hope this will help you!
Thanks for the reply. In fact, this error in the log does not interfere with normal operation, I sent another request to you. The problem is that the surface doesn’t appear in a Linear container, because that’s what I need. I sent the markup and the code to you.
// use alternative RenderSurface implementation which uses Canvas API for drawing
Does not solve the problem
Please login first to submit.