Mobile and Embedded

@Dooham It is solved. It was because I need to use the kit arm or arm64 depending on the version of your device. I was used the version x86 and that was the problem.

@SteMMo said in Compiling app for TinkerBoard (Linaro/Debian) from Windows: Or is only possible from a Linux machine? Not sure if it's only possible with Linux, but I'd say it will be the best case, since I bet you'll find tons of examples of cross-compiling Qt (not only for your board) that are based on Linux. If you can use a VM, I'd say you'll save lot of time and effort compared to use Windows as your host OS for cross-compiling.

@getgo said in qtmultimedia cross compile can't find gstream: i just directly copy alsa folder from host to mount sysroot Sorry if I'm wrong, but it looks like you should do the other way around when cross-compiling. I mean, you install the support libraries and headers in your TARGET device, and then you rsync to your sysroot folder in HOST machine. That way you'll be using the proper objetcs for your target architecture.

@abbassi Hi, Have you got solution for this? If yes, what is the solution..please let me know..Thankyou

SO. An update for anyone who may come across this later. Screen rotation: I couldn't figure out a way for the QPlatformScreen subclass I was dealing with to continuously monitor the accelerometer and update the orientation QPlatformScreen::orientation(). I only saw a call into this function during initialization and not continuously as I had hoped. QGuiApplication::primaryScreen()->orientation() never called into the QPlatformScreen implementation so no querying of the accelerometer was done in the app. Since I wasn't making progress this way, I went back to the original method of an outside process monitoring the accelerometer and notifying Qt App over DBus. Next, upon receipt of this message, I call QWindowSystemInterface::handleScreenOrientation(screen, orientation) (not part of the API, could change with versions) which allows the entire application to then know the orientation by querying QScreen::orienation(). QPlatformScreen then can do rotation itself in hardware based on current orientation. Touch Event Rotation Handling: Somewhat working, not complete. Installed an event filter on QApplication, caught touch events as they came in, created new QTouchEvent based on received events with transformed coordinates, and sent these new events along with QCoreApplication::sendEvent and returned true for handling of original event. Was baffled as when orientation was inverted, the filter wasn't activating anywidgets. Learned default behavior of events in QWidget is to synthesize mouse events if a QTouchEvent goes unhandled, and this is what is actually handled in QWidgets. So modified filter to only work on mouse events: this required x and y transformations of course but also setting source to MouseEventSynthesizedByApplication so as it was passed to each widget it wasn't continually transformed (if synthed by app, don't do x/y transformation again). Gestures are still broken, as I believe I still need to handle touch event transformation, but without breaking the synthesis of QMouseEvents by Qt. (PanGesture still is recognized when inverted, but pans in the incorrect direction). If anyone has suggestions on this last part, let me know!

The java code had a memory leak in the code: public String execute(String channelName) { // String [] value = new String[50]; double [] pv_data = new double[50]; try { // initialize context //initialize(); Context context = null; JCALibrary jca = JCALibrary.getInstance(); context = jca.createContext(JCALibrary.CHANNEL_ACCESS_JAVA); // Create the Channel to connect to the PV. Channel channel = context.createChannel(channelName); .... .... .... // calling this before returning solved issue context.destroy();

Hi and welcome to devnet, You might be asking questions for situations that may have not been encountered yet. They are indeed interesting. I would suggest bringing them to the interest mailing list. You'll find there Qt's developers/maintainers. This forum is more user oriented.

You seem to use a version of the emsdk that is not mentioned in the Qt for Web Assembly wiki entry. Did you try to use one of these ?

Ok, then it would have been better to explain that from the start. What size is your database ? If not too big, you can put it in Qt's resources system and then copy that file from the resource to a suitable location given by QStandardPaths. You may have to create the folder given before copying the database file over there.

Hi again, I could not figure out how to retrieve this clipped area, I searched about setting margin of plotting area but no success. However at least, I managed to show points label totally with these codes; series->setPointLabelsVisible(true); series->setPointLabelsColor(Qt::black); series->setPointLabelsClipping(false); series->setPointLabelsFormat("@yPoint"); Maybe that helps to others ! Thanks

Someone might have ideas if you told in detail what your device is.

@Pablo-J-Rogina I will look into it.