On 13 Sep 2013, at 7:53 AM, Duan Fugang-B38611 wrote:
> Hi, all,
>
> We use the X.Org X Server 1.14.0 + QT4.8.5 to do one demo, but I catch one
> issue: multi-touch message is not handled by “close” button.
>
> I use egalax touchscreen for the multi-touch test.
> After kernel up, evtest tes
Hi, all,
We use the X.Org X Server 1.14.0 + QT4.8.5 to do one demo, but I catch one
issue: multi-touch message is not handled by "close" button.
I use egalax touchscreen for the multi-touch test.
After kernel up, evtest test the multi-touch message, all pass. Use xinput to
do the test, also pa
iago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
Url
Hi, all,
We use the X.Org X Server 1.14.0 + QT4.8.5 to do one demo, but I catch one
issue: multi-touch message is not handled by "close" button.
I use egalax touchscreen for the multi-touch test.
After kernel up, evtest test the multi-touch message, all pass. Use xinput to
do the test, also p
Hi, all,
We use the X.Org X Server 1.14.0 + QT4.8.5 to do one demo, but I catch one
issue: multi-touch message is not handled by "close" button.
I use egalax touchscreen for the multi-touch test.
After kernel up, evtest test the multi-touch message, all pass. Use xinput to
do the test, also pa
On quinta-feira, 12 de setembro de 2013 21:06:03, John Layt wrote:
> * Choose either local msecs or epoch msecs, if epoch then that change can't
> be done for 5.2
Choose the easiest for you to implement. We're running out of time, so I'd
rather stick to the implementation you have and your best
I got stracktrace. It is as you predicted glDrwaElements. Is there any
possibility to make some kind of workaround patch to make it work on
emulator (I suppose it is emulator GL issue), perhabs by turning off some
optimizations and so on? I would like to add such patch to rpm emulator
package until
On 9/12/13 9:06 PM, "John Layt" wrote:
>Hi,
>
>Another QDateTime email. I'm still trying to get a fully working
>reimplementation of QDateTime as well as the QTimeZone support in for
>5.2, but
>there's a couple of issues outstanding.
>
>Storage format / Change of System Time Zone behaviour: My
On Thu, Sep 12, 2013 at 9:24 PM, Knoll Lars wrote:
> We might be able to simply cache the time zone offset once and cache it.
> Then it should be at the same speed.
This would also probably provide hidden wins in various places, making
changes like b9ef4a9c3047228ec007ac81ff0a304f8cc274b7 in qtba
Thanks Lars!
It seems like a big step, indeed, after reading it on the blog. I (as a
developer) appreciate the concern about code migration in the future,
which I think (I may be wrong) will not be a PITA since Blink came as
Webkit fork (sharing the same root and bla bla bla).
But, I have so
On quinta-feira, 12 de setembro de 2013 09:38:16, achart...@fastmail.fm wrote:
> Thiago - The qMetaTypeId documentation
> (http://qt-project.org/doc/qt-5.1/qtcore/qmetatype.html#qMetaTypeId)
> specifically states that the type registration using this function is
> resolved at compile-time, not run-
Hi,
Another QDateTime email. I'm still trying to get a fully working
reimplementation of QDateTime as well as the QTimeZone support in for 5.2, but
there's a couple of issues outstanding.
Storage format / Change of System Time Zone behaviour: My current changes on
Gerrit for storing as msecs
We're going to meet Alexis and Kenneth in two weeks. I was planning on talking
to them about exactly that :)
Simon
Fra: Thiago Macieira
Sendt: 17:44 torsdag 12. september 2013
Til: development@qt-project.org
Emne: Re: [Development] Qt WebEngine
On quinta-feira, 12 de setembro de 2013 12:03:39,
> Message: 1
> Date: Wed, 11 Sep 2013 19:12:26 -0700
> From: Thiago Macieira
> Subject: Re: [Development] constexpr and qMetaTypeId<>()
> To: development@qt-project.org
> Message-ID: <3962396.DaoebYs1tu@tjmaciei-mobl2>
> Content-Type: text/plain; charset="us-ascii"
>
> On quarta-feira, 11 de sete
Hi,
the FAQ states: "We intend to make QtWebEngine available on all
platforms that the upstream Chromium project supports, with the
exception of Android. This also means iOS won’t be supported."
So what are the plans for Android and iOS? We currently do not have
QtWebkit on those platforms and su
On quinta-feira, 12 de setembro de 2013 12:03:39, Knoll Lars wrote:
> Hi,
>
> As many of you know, we've been doing some research on a (chromium based)
> new web engine for Qt during spring and summer. I wanted to let you know
> that we've now come to the conclusion that we want to continue these
2013/9/12 Sletta Gunnar
>
> On Sep 11, 2013, at 11:12 PM, Tomasz Olszak
> wrote:
>
> > Hi,
> > I have strange issue running most recent Qt sources on Tizen emulator
> (qemu i586).
> > Also I know that there are issues with supporting HW acceleration. For
> example I need to export QML_BAD_GUI_RE
On Sep 11, 2013, at 11:12 PM, Tomasz Olszak wrote:
> Hi,
> I have strange issue running most recent Qt sources on Tizen emulator (qemu
> i586).
> Also I know that there are issues with supporting HW acceleration. For
> example I need to export QML_BAD_GUI_RENDER_LOOP=1 because multithreaded
>
Hello Sean,
Could you explain what your plans are with the release?
We're getting the other modules into shape and it would be nice to get a clear
story about Qt 3D.
On the documentation side, we would need:
-product information (module name, Essential/Add-on/Tech Preview status, and so
on.)
-
Hi,
As many of you know, we've been doing some research on a (chromium based)
new web engine for Qt during spring and summer. I wanted to let you know
that we've now come to the conclusion that we want to continue these
efforts in the future.
Please check
http://blog.qt.digia.com/blog/2013/09/12
Hi,
I'm wondering whether the 'offscreen' platform plugin is of any use on Windows?
I couldn't get it to behave on Windows (crashes on startup). And the Qtestlib
documentation actually states " Currently the offscreen platform plugin is only
fully supported on X11.".
If nobody objects, I'd lik
On Wednesday, September 11, 2013 14:29:44 achart...@fastmail.fm wrote:
> Hello,
>
> I'd like to use qMetaTypeId<>() in a constexpr expression. I have my own
> custom type declared as such:
>
> class MyCustomClass : public QObject
> {
> Q_OBJECT
>
> // ...
> };
>
> Q_DECLARE_METATYPE(M
AFAIK, nesting event loops should be used with a great carefulness and in
very limited set of cases, since it may break the expected order of event
handling, i.e. when used as a signal waiter.
Dunno if this changed since Qt 4.x, though.
Regards,
Konstantin
2013/9/12 André Somers
> Op 11-9-2013
23 matches
Mail list logo
