I apologise for this being done out of the thread order but I didn't have the
original in my mail client to reply to this.
Den 11-03-2015 kl. 11:37 skrev Bernhard:
Hi!
We are a very small startup company (having part time Qt developers only).
We are experiencing that non-fatal bugs as
I started using Qt with 4.0.0 and pretty much fell in love with it...
seems my cutie is letting itself go ;-)
I know how you feel. And I started with 0.4 :)
:-)
However, since 5.3 it's improved a lot. QML is still buggy to a point
where it's
quality is way lower than the rest of the
Hi,
I have a QSqlQueryModel, which I feed a query with setQuery(const QSqlQuery
query).
Works great the first time I do this. Works too, if I use setQuery(const
QSqlQuery query)
a second+ time to change the query. However, after the 1st time I get on the
console:
?libqsqlpsql.so? -- 0 --
Den 04-03-2015 kl. 19:39 skrev Scott Aron Bloom:
-Original Message-
From: interest-bounces+scott.bloom=onshorecs@qt-project.org
[mailto:interest-bounces+scott.bloom=onshorecs@qt-project.org] On Behalf
Of Thiago Macieira
Sent: Wednesday, March 04, 2015 9:44 AM
To:
Den 08-03-2015 kl. 11:58 skrev Guido Seifert:
I am just curious. In one of my old projects I replaced all SIGNAL/SLOT
connections with the newer function pointer api.
In theory I now could remove all the 'public/protected/private slot' markers
from my .h files. Now I am wondering, if this
Den 11-03-2015 kl. 21:36 skrev Bernhard:
I did not say that we *cannot* continue with Qt. What I say is that it gets
more painful and difficult.
For our current projects there are no options anyway.
But there may be projects in the future at other companies where I will get
asked again What
Qt does exactly what you ask for: it requests a 2.0 context. Now since
implementations are free to return a later version that is backwards compatible
with the requested, getting a 3.0 or 3.1 context is perfectly fine (and is the
standard behavior you will get with any driver that supports ES
Just discovered: This problem exists only when I use prepared queries. Same
code without a prepared query works as expected. So definitely not my bug.
I write a bug report.
Guido
___
Interest mailing list
Interest@qt-project.org
Bo:
I am quite shocked.
Is 5.4.1 QML so buggy as to be un-usable for mobile development?
Is the 5.4.1 mysql support so unstable as to be un-usable?
Are you saying that widgets is STILL the way to go for mobile in 5.4.x+?
Does Viking software survive in 5.4.x + only via Enterprise support?
Den 12-03-2015 kl. 10:15 skrev m...@rpzdesign.com:
Bo:
I am quite shocked.
Is 5.4.1 QML so buggy as to be un-usable for mobile development?
No, it's not unusable. I said the quality is way lower, that's certainly
not the same as unusable. In the Qt community we're spoiled with quality
I never ever heard of anything been done through it, though, which is a
pity,
but it's how things are. If you think about it, the most likely reason why
this
didn't happen, is because they did not gather enough money.
You are probably right. Maybe there would be a better chance if bounties
Hi,
I have developed an app using fixed measures in pixels for certain parts. It is
working well for iPad and 7” and 10” mdpi android devices.
The problem is that certain android devices have huge resolutions for the same
amount of physical sizes.
What are the technics uses to scale the
On Wed, Mar 11, 2015 at 07:22:37PM +0100, Alejandro Exojo wrote:
El Wednesday 11 March 2015, Bernhard escribió:
However currently both sites seem unusable. gitbounty says nothing more
than Coming Soon... and bountysource display an effectively empty page
when clicking on some Qt issue (on
On 12 Mar 2015, at 10:22, Nuno Santos nunosan...@imaginando.pt wrote:
Hi,
I hope so.
The thing is that my other app that is already on the store works perfectly
and prices are fetched…
Just wondering…
On 12 Mar 2015, at 10:20, Robert Iakobashvili corobe...@gmail.com wrote:
I would not consider that as a hack at all. It is perfectly fine. There’s
nothing wrong with using ESSL1 shaders with ES 3.0+, as long as you do not rely
on features that need the newer language features. Qt Quick for examples uses
ESSL1 compatible shaders always and does not include ESSL3
Can you take a look at http://community.arm.com/message/16669
As you have said, Using GLSL 3 with GL_OES_EGL_image_external is not
permitted, but using GLSL 1 with GL_OES_EGL_image_external under opengl es
3 context is more like a hack according to the post.
Am 12.03.2015 um 11:13 schrieb Liang Jian jianlian...@gmail.com:
But As you have said Qt will request 2.0 context, and it is the implentation
choose openges 3 context, then It seems that it is a bug of the driver.
Just to repeat and clarify: the fact that the driver returns you an
Hello,
I have a slight problem and was hoping that someone here could provide
some advice on how to handle/solve this.
Let me sketch my problem in plain old ASCII art here.
+--++---+
| | ++ | |
|
In QML I'm using Screen.pixelDensity
So a minimum width of touch area is about Screen.pixelDensity*7, which
will be 7 mm in pixels, and the number comes from some old Nokia
ergonomics study.
Now some low end Android devices report bogus values, suffering from
illusions on grandeur, but it
Den 12-03-2015 kl. 14:57 skrev maitai:
If an app needs to be qml for mobile and qwidgets for PCs, then the
whole concept of portability is broken.
Please don't try and claim that my concepts are broken :) I have
multiple applications for multiple customers. They are not related in
any way.
Hi guys,
Might be related to the DNS problems Apple experienced
http://arstechnica.com/apple/2015/03/apple-dns-error-responsible-for-ongoing-itunes-app-store-outages/
Samuel
On 12 mars 2015, at 14:02, Harri Pasanen ha...@mpaja.com wrote:
FYI, I'm currently experiencing something similar with
If an app needs to be qml for mobile and qwidgets for PCs, then the
whole concept of portability is broken.
As far as we are concerned, we used QWidgets for mobile deployment too,
without too much troubles. At least it's the same code (with a few
#ifdef, ok) for all platforms.
We have our
On Thursday 12 March 2015 08:56:08 Thiago Macieira wrote:
On Thursday 12 March 2015 09:10:40 Bernhard wrote:
Well I do not use QML. Actually am writing widget based applications only.
Most of my issues are in conventional parts of Qt like building the
framework, (MySQL) database support,
On Thursday 12 March 2015 10:31:56 Bo Thorsen wrote:
Does Viking software survive in 5.4.x + only via Enterprise support?
No. Viking Software is a Qt consulting company. I have 18 years of Qt
coding experience. Support is not required
In other words, Bo has more experience with Qt than I
Bo Thiago:
I really appreciate both of you guys sharing so freely on the email lists.
It really helps to have people honest opinions and viewpoints since the
importance of shared experiences, both from newbies and veterans helps
calibrate that state of things.
Cheers to you both,
md
On
On Thursday 12 March 2015 09:10:40 Bernhard wrote:
Well I do not use QML. Actually am writing widget based applications only.
Most of my issues are in conventional parts of Qt like building the
framework, (MySQL) database support, widgets, meta type system, missing
stuff (global shortcuts
Am 12.03.2015 um 14:57 schrieb maitai mai...@virtual-winds.org:
If an app needs to be qml for mobile and qwidgets for PCs, then the
whole concept of portability is broken.
Uhm... why? The UI layer - in the best case - is just a small part of the
application and the entire business logic
On Thursday 12 March 2015 20:16:01 Gunnar Roth wrote:
Hi Thiago,
Am 12.03.2015 um 16:56 schrieb Thiago Macieira
thiago.macie...@intel.com:
As QtCore maintainer, I resent that. I fix almost every real bug in QtCore
almost immediately.
Sadly my long standing qtcore-bug seems to fall
On Thursday 12 March 2015 18:29:37 Nuno Santos wrote:
Hi,
I need to deploy an app compatible with 32-bit computers running OSX. The Qt
installation must compiled from the source to have 32 bit of Qt?
Yes.
If so, what is the most quick and straightforward configure command to do
it?
On Thu, 12 Mar 2015 13:38:06 +0100
David Heremans david.herem...@intersoft-electronics.com wrote:
If the panels could be made to only resize when a users drags the
splitter handles around this would probably solve my problem, but I
don't seem to find such an option in the documentation...
Is
How can I get the Qt commercial sources?
I'm using commercial Charts.
Sent: Thursday, February 05, 2015 at 9:06 PM
From: Thiago Macieira thiago.macie...@intel.com
To: interest@qt-project.org
Subject: Re: [Interest] Installing on a headless server
On Thursday 05 February 2015 21:04:34 Jason
On Wed, Mar 11, 2015 at 11:22 AM, Alejandro Exojo s...@badopi.org wrote:
El Wednesday 11 March 2015, Bernhard escribió:
However currently both sites seem unusable. gitbounty says nothing more
than Coming Soon... and bountysource display an effectively empty page
when clicking on some Qt issue
My thumbs up for Qt Core.
There is so much good stuff in Qt Core that it is worth using even if
the UI is non Qt.
So keep up the good work!
Harri
On 12/03/2015 16:56, Thiago Macieira wrote:
On Thursday 12 March 2015 09:10:40 Bernhard wrote:
Well I do not use QML. Actually am writing widget
Hi,
I need to deploy an app compatible with 32-bit computers running OSX. The Qt
installation must compiled from the source to have 32 bit of Qt?
If so, what is the most quick and straightforward configure command to do it?
Thanks in advance,
Regards,
Nuno
Hi Thiago,
Am 12.03.2015 um 16:56 schrieb Thiago Macieira thiago.macie...@intel.com:
As QtCore maintainer, I resent that. I fix almost every real bug in QtCore
almost immediately.
Sadly my long standing qtcore-bug seems to fall into the other category. Its
QTBUG-27765
QSharedMemory loses
FYI, I'm currently experiencing something similar with a non-Qt iOS app.
The new in-app items Apple approved last night are not visible, just an
old one.
I've been wondering if I had messed up something, but this sounds too
much like a co-incidence.
/Harri
On 12/03/2015 11:22, Nuno Santos
I have filed a bug report to PowerVR
On Thu, Mar 12, 2015 at 6:39 PM, Till Oliver Knoll
till.oliver.kn...@gmail.com wrote:
Am 12.03.2015 um 11:13 schrieb Liang Jian jianlian...@gmail.com:
But As you have said Qt will request 2.0 context, and it is the
implentation choose
Thx Thiago!
Regards,
Nuno
On 12/03/2015, at 21:29, Thiago Macieira thiago.macie...@intel.com wrote:
On Thursday 12 March 2015 18:29:37 Nuno Santos wrote:
Hi,
I need to deploy an app compatible with 32-bit computers running OSX. The Qt
installation must compiled from the source to have
On Thursday 12 March 2015 23:46:32 René J.V. Bertin wrote:
On Thursday March 12 2015 14:32:00 Thiago Macieira wrote:
It has 3 Votes and 4 watches. I provided a patch as attachment, 2 years
ago, nothing happened.
We have to ignore patches as attachments to bug reports if they are non-
On Thursday March 12 2015 14:32:00 Thiago Macieira wrote:
It has 3 Votes and 4 watches. I provided a patch as attachment, 2 years ago,
nothing happened.
We have to ignore patches as attachments to bug reports if they are non-
trivial. If you want the patch to be processed, submit it via
On 11/03/15 22:52, Michael Jackson wrote:
So if i have my executable in [install]/bin and libQt5Core.so.5 in
[install]/lib then I should be able to just generate a package by copying the
Qt libraries from the Qt 5.4.1 installation location. I am used to stuff like
this on OS X where I have
Hi,
I’m desparating a bit so i’m trying to gather all the information I can about
this.
I have developed an app for iOS and Android and I have used in app purchasing.
I have already done an app a couple of months ago with in app purchases. It was
deployed with Qt 5.3.0. Everything working
Now qt-android will create an OpenGL ES 3 context if that ES3 is
supported by the devices even if I have call
QSurfaceFormat::setVersion(2,0). Is it a way to just create the specific
version I wanted using QOpenGLContext?
The reason why I care about that is: I need to use SurfaceTexture
43 matches
Mail list logo
