Meaning I can sell the desktop apps without having to distribute my code and
into the Windows and Mac App Stores (WITHOUT having to pay my lawyer thousands)?
> On 18 Jul 2015, at 16:43, Thiago Macieira wrote:
>
>> On Saturday 18 July 2015 13:04:45 John C. Turnbull wrote:
>> The problem even w
On Saturday 18 July 2015 13:04:45 John C. Turnbull wrote:
> The problem even with this extension for the Indie Program is that it *only*
> allows you to use Qt to develop *mobile* apps. The appeal of Qt is its
> cross-platform ability but if you are using it *just* for mobiles then you
> will get
On Friday 17 July 2015 20:38:59 varro wrote:
> I'm writing a Qt application using the ruby bindings in which I need
> to be able to support entering non-ASCII data (accented characters and
> so on). Googling seems to indicate that the normal way of handling
> this is using ibus to provide an input
Hi,
I’m not investing to much time with this problem because my apps are stable in
Qt 5.4 and I don’t want to rush into Qt 5.5.
However, when I have time, I’m trying to understand what is making this strange
phenomena happening.
The problem is, when building for iOS, it is somehow replacing th
Dear md,
That's all well and good re using native compilers but (from what I hear),
Qt apps on iOS and Android are buggy, lacking features, big, slow and often
"appear" foreign to that OS.
I will admit that this is just what I have read but I have read it many
times.
Further, I dispute your asse
Dear Mr Turnbull:
I would like to add some color to your assertion that "mobile" support
is "embryonic" at best.
The compilers used by Qt are the NATIVE compilers for
IOS/OSX/Android/Windows/Tizen/Linux/NaCL/embedded/etc/etc/etc
There can be nothing more ROCK solid than using the manufacturers
The problem even with this extension for the Indie Program is that it *only*
allows you to use Qt to develop *mobile* apps. The appeal of Qt is its
cross-platform ability but if you are using it *just* for mobiles then you
will get a better result with a framework designed specifically for mobiles
Hello:
I am having a text rendering problem.
The following code creates a QLabel and QGraphicsTextItem.
The QLabel text is 60 pt. The QGraphicsTextItem text size is 6 pt,
but then the view is scaled up by 10x. So, in the end both
pieces of text are the same size on the screen.
For me the QLabel
On 7/17/2015 4:56 PM, Nicola De Filippo wrote:
> yes, but i think if he wants update the app in the future he need other
> month/license. N.
I could be wrong, but that is not the impression I got. I understood that
purchasing before the end of August means you have the license until you stop
Hi,
> Il giorno 18/lug/2015, alle ore 00:44, Bob Hood ha
> scritto:
>
> On 7/17/2015 3:38 PM, Nicola De Filippo wrote:
>> real case yesterday, a my friend must develop a simple app for Android, IOS
>> and windows for 2.500 euro (very lower budget). He asked me a tool
>> cross-platform, i say Q
On 7/17/2015 3:38 PM, Nicola De Filippo wrote:
> real case yesterday, a my friend must develop a simple app for Android, IOS
> and windows for 2.500 euro (very lower budget). He asked me a tool
> cross-platform, i say Qt, but i had to tell the truth, from September do not
> know how you will pay
Hello,
I’m trying to update Qt 5.5 for all my project and I’m having very bad behavior
of StackView.
What has been changed on StackView that may break compatibility ?
All my app has a center item that it’s a StackView and I push/pop element on
that. But It doesn’t work anymore.
I didn’t use any s
I'm writing a Qt application using the ruby bindings in which I need
to be able to support entering non-ASCII data (accented characters and
so on). Googling seems to indicate that the normal way of handling
this is using ibus to provide an input method. Although I've
installed ibus, it doesn't st
Hi,
>
> I see that power of Qt comes from community, also in mobile. Community
> itself does not create huge revenue but a lot of business grown
> from
> community. There is no sense to say NO for indie or small developers
> unless intention is kill all mobile Qt.
>
real case yesterday, a my fr
Yeah there are various issues:
https://bugreports.qt.io/issues/?jql=text%20~%20%22android%20qmessagebox%22
QTBUG-35545 is probably the one you’re interested in.
On 16 Jul 2015, at 17:52, Edward Sutton wrote:
> Hi Robert,
>
> Thanks, I will create one on my Qt account portal.
>
> ( Using Qt 5
Ok… found:
QMAKE_CFLAGS += -fobjc-arc
Thanks!
Nuno Santos
Founder / CEO / CTO
www.imaginando.pt
+351 91 621 69 62
> On 17 Jul 2015, at 11:03, Nuno Santos wrote:
>
> Ok, I have found the problem. The lib comes with a .pch file with the
> following content:
>
> //
> // Prefix header for all s
Ok, I have found the problem. The lib comes with a .pch file with the following
content:
//
// Prefix header for all source files of the 'AEAudioController' target in the
'AEAudioController' project
//
#ifdef __OBJC__
#import
#endif
I have added the qmake variable:
PRECOMPILED_HEADER +=
Hi,
I’m trying to add an Objective-C project as .pri
However, during compiling for iOS-clang, it complains about not knowing about
NSObject and BOOL types. Isn’t this supposed to be part of the iOS-clang
compilator knowledge?
This is my .pri file. I have added TheAmazingAudioEngine as a git s
18 matches
Mail list logo
