On 14/07/15 01:01, Gian Maxera wrote:
> If you can use dynamic link … use dynamic link !! There is only advantages
> over static link.
>
>
What advantages on a mobile device? You aren't sharing the libraries
with other apps, and you're guaranteed not to get any code stripping...
Hamish
That would be absolute insanity to think anything other than a robust
mobile capability is essential to the future viability of QT.
md
On 7/11/2015 5:00 AM, Nicola De Filippo wrote:
> Hi,
>>
>
> if it’s the status quo, maybe is better that the Qt company leave the mobile
> market and work only
Adding to Jason words.
Clearly a device with an API level lower than the one you specify cannot
install your app (or simply see it in the play store). That's why usually
the minimum sdk is also one of the minimum API available: target as many
devices as possible. Targeting ICS does not narrow the
Min SDK: The minumum version you are willing to target. May be missing some features.
Target SDK: The SDK with all the APIs you need.
Build SDK: The SDK you are building with.
In general Min SDK==Target SDK unless you have code to invoke newer SDK features.
Build SDK >= Min SDK. The SDKs
Has anyone on the list worked with OpenSceneGraph and Qt. I'm currently
working on an application that works as a virtual campus tour. It was
originally written in Qt/OpenGL and was eventually integrated with
OpenSceneGraph which manages all of the OpenGL calls, but Qt is used to run the
m
Qt is supposed to create a default launch screen, but every time I change it I
just get a blank (black) screen. I tried a VC with just green as background and
nothing works.
Is there a minimal working example someone can share of a non-default screen?
Many thanks!
__
Hi,
Can one advise me on the proper settings for min sdk, target sdk and build sdk
for Android?
I want my min SDK to be API 14, for that reason i’m also targeting to API 14
and i’m building with API 21.
Is there any problem with this? Will this allow me to run on the latest Android
OS?
Than
If you can use dynamic link … use dynamic link !! There is only advantages over
static link.
on iOS, is the Apple policy that forbid that ! :-( Why ??? Maybe because using
dynamic linking you can embed executables and run them inside the app.
Ehehe… it was a trick I used into an Android app for
Hello,
Now that I have a nice indie license (thanks again for giving us a grace
period), I am wondering whether I should link qt libs for android
statically or leave it as it is (bundled in apk)... Is there any
advantage (performance for instance) in doing so?
I understood that for iOS anyway
Hi,
You can try to start the dragging with "drag->exec(Qt::CopyAction);" instead of
"drag->exec();". The latter is a MoveAction by default which may be transformed
into a CopyAction in InterProcess Drag-And-Drop..
- Michael.
From: interest-bounces+sue=sf.mpg...@qt-project.org
[mailto:interes
On Saturday 11 July 2015 00:36:18 Nuno Santos wrote:
> Thiago,
>
> I don’t know what to look for. The output follows attached.
I can't see anything either. Is this the one that you had problems with?
Anyway, check any hidden files like .qmake.conf and .qmake.cache
--
Thiago Macieira - thiago.ma
Hi
I have a QListWidget that I need to support drag and drop
At the moment I have it so that I can drag an item from an different widget and
have it added to the list
But when I drag an item internal to the widget the target of the drop seems to
be deleted from the list
I need a list widget tha
Hi,
Anybody have any tips to detect upon which screen the application or the
windows is currently running on into multiple screen setup? The setup is a
UHD display as secondary monitor and an Full HD main monitor.
I try to launch the application on both screen and the Screen from import
QtQuick.Wi
On 9 July 2015 at 21:35, Jason H wrote:
>> Sent: Thursday, July 09, 2015 at 4:26 AM
>> From: "Jaroslaw Staniek"
>> To: interest@qt-project.org
>> Subject: [Interest] Exposing types to the QJSEngine in Qt 5.5
>>
> ...
>> Adding qRegisterMetaType() prior to engine instantiation does not
>> help.
>
Call QCoreApplication::setAttribute(Qt::AA_UseOpenGLES) before anything else,
most importantly before constructing the Q(Gui)Application.
Right now you are making your request way too late, after WebEngine (and
potentially others) have already run OpenGL related code.
Best regards,
Laszlo
On Monday 13 July 2015, Shantanu Tushar wrote:
> Hi,
>
> I tried passing that to the my app's executable (verified using process
> explorer that the cmdline argument was there), it still loads opengl
> instead of egl. The following gets passed to QtWebEngineProcess-
>
> --type=renderer --enable-
Yes!
Nuno Santos
Founder / CEO / CTO
www.imaginando.pt
+351 91 621 69 62
> On 13 Jul 2015, at 10:18, maitai wrote:
>
> Hello,
>
> Did you make sure that your x86 version number is higher that the arm's one?
>
>
>
> Le 13-07-2015 11:04, Nuno Santos a écrit :
>
>> Hi,
>>
>> I'm uploadin
Hello,
Did you make sure that your x86 version number is higher that the arm's
one?
Le 13-07-2015 11:04, Nuno Santos a écrit :
> Hi,
>
> I'm uploading the android version of my app to Google Play for beta testing.
> While I can run it on my test Bq Aquaris E5 FHD phone, when I try to in
Hi,
I’m uploading the android version of my app to Google Play for beta testing.
While I can run it on my test Bq Aquaris E5 FHD phone, when I try to install it
via Google Play it says the device isn’t compatible.
I have asked Google why it gets this message and they told me:
"I’ve looked into
Hi John,
IMHO,
if ("You already have a Qt desktop application or planning it" && "You
are planning to use Qt beyond GUI - Networking, Containers, QString,
etc.")
{
"Yes, it is worth to do it."
}
else
{
Since it is still rather buggy, be ready to spend your time on workarounds.
Since m
Hi,
I tried passing that to the my app's executable (verified using process
explorer that the cmdline argument was there), it still loads opengl
instead of egl. The following gets passed to QtWebEngineProcess-
--type=renderer --enable-threaded-compositing --no-sandbox
--use-gl=desktop --enable-d
21 matches
Mail list logo