Mobile and Embedded

of course i already read it. but i could build and deploy some nfc examples of qt 5.4 on my android phone and it did run without any errors! but actually i'm not sure if it really works on android. -locke [quote author="kolegs" date="1415347785"]acording to the docs http://qt-project.org/doc/qt-5/qtnfc-index.html it does not support Android or iOS[/quote]

solution: https://bugreports.qt-project.org/browse/QTBUG-40458

sierdzio, thanks for a repley! i installed qt 5.4 beta on my windows system and deployed a new app on my android phone. i see, yes, the square of checkbox gots a little bigger than the past. but still smaller than its text. except for that, there's nothing different. my radiobutton and combobox UIs are still small. is there any other special setting for that? i don't know what to do for it.

Then it looks like your going to also be interested in the Scene Graph part

It depends if you are writing the QML by hand or using the qml designer. The video format supported will depend on the backend, so if's linux, it should be what gstreamer supports.

[quote author="ltr6" date="1415182621"]What does your AndroidManifest.xml look like? I think in the <activity> you have to set android:name="de.myApp.Mailer"[/quote] You are the man ;-) Thank you. That was exactly the problem. I just added android:name="de.myApp.Mailer" in <activity> of the AndroidManifest.xml and now the Mailer java object gets instantiated like expected. To allow another app (some mailing app) to access the file to attach we must make sure the file is not in the sandboxed app environment. I use for file creation: @ QString tempDir = QStandardPaths::writableLocation(QStandardPaths::GenericDataLocation); @ Important: Need to rebuild project Thank you

here is something for you, package com.exercise.AndroidOrientation; import android.app.Activity; import android.content.pm.ActivityInfo; import android.os.Bundle; import android.view.View; import android.widget.Button; public class AndroidOrientationActivity extends Activity { /** Called when the activity is first created. */ @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.main); Button buttonSetPortrait = (Button)findViewById(R.id.setPortrait); Button buttonSetLandscape = (Button)findViewById(R.id.setLandscape); buttonSetPortrait.setOnClickListener(new Button.OnClickListener(){ @Override public void onClick(View arg0) { // TODO Auto-generated method stub setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_PORTRAIT); }}); buttonSetLandscape.setOnClickListener(new Button.OnClickListener(){ @Override public void onClick(View arg0) { // TODO Auto-generated method stub setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_LANDSCAPE); }}); } }

QScreen *s = app.primaryScreen(); qDebug() << "nativeOrientation: " << s->nativeOrientation(); qDebug() << "orientation: " << s->orientation(); qDebug() << (s->isLandscape(s->nativeOrientation()) ? "nativeOrientation lanscape" : "nativeOrientation not lanscape"); qDebug() << (s->isLandscape(s->orientation()) ? "orientation lanscape" : "orientation not lanscape"); qDebug() << (s->isPortrait(s->nativeOrientation()) ? "nativeOrientation portrait" : "nativeOrientation not portrait"); qDebug() << (s->isPortrait(s->orientation()) ? "orientation portrait" : "orientation not portrait");

I didn't resolved, sometime it does crash I don't understand.... but when I see a little delay while I close windows it do crash. The error is very generic. Have someone an idea? My Best Regards

Thanks; will mark this a Solved.

ahh okay :-) Have Fun !

This might be a bug since I managed to do a workaround, as it only occurs if menubars are changed via @setMenuBar(QMenuBar *menubar)@ without deleting the current menubar and if there are any methods that modify the widgets inside central's widget layout(deleting,adding) before adding a new menubar. In case someone bumps into this, here is my workaround: @/* this is the first menubar which I set by default, before login and after the the user disconnects / void mainwindow::setMenuBar1(){ / do nothing here / if(this->menuWidget()!=NULL){ delete this->menuWidget(); mb=new MenuBar1(this); setMenuBar(mb); } else{ mb=new MenuBar1(this); setMenuBar(mb); } / in case it's needed do something here */ } /* this is the menubar which I set after login / void mainwindow::setMenuBar2(){ / do nothing here / if(this->menuWidget()!=NULL){ delete this->menuWidget(); mb=new MenuBar2(this); setMenuBar(mb); } / in case it's needed do something here */ }@ This workaround works 80%-90% of the time unfortunately. If someone care to help I'm open for tips.

I found the site below and follow what they are doing. http://doc.qt.digia.com/4.6/network-broadcastsender.html I found my problem is because i created the socketUDP class object inside Mainwindow constructor, application cannot received. When i put the object creation outside mainwindow (in main.cpp), data is received successfully. Thanks

Hi, I am doing the same thing. I am working with the QGraphicsView/Scene. I want to add invisible rectangular areas, that has multiple properties, like clickable, repaintable, updatable, etc. Are only the event handlers option here or SIGNAL/SLOT mechanism still can be used?

When you say "not possible to be hardware independent", are you referring to the qmake.conf edition ? That's why I suggested to ask the Toradex folks whether they were aware of that issue.

I've had problems getting a cross compile to work with the latest 3.14.y kernel builds on BBB. I was using the Linaro toolchain on 32 bit debian linux to cross compile. Even though I was using a sysroot image for the cross compile, some of the kernel includes would come from the Linaro tool and it would fail. Compile the Qt library on the BBB. It takes about a day and a half, but it detects the Sgx graphics libraries and enables EGLFS.

Hi, You can compile by yourself following this tutorials. However if you compile Buildroot, or Yocto you'll get all the components to make your system and develop applications for it. By generating SDK on Yocto you have all the you needs to cross-compile and deploy your application, the same happens with the generated qmake with buildroot. But the most valuable thing you win by doing this is that your system generates automatically. If you need a Qt's library, you just add this in Yocto or Buildroot and both development's and system's machines will be updated with the new package. I hope I have helped you.

The documentation is being updated for iOS