Hi,
> I need to have a vote on a implementation detail regarding filtering of
> wildcards categories.
> Let's say you have a category defined and a wildcard category as well.
> A: Do you think the order in the configuration file plays an important rule or
> B: If you set specific a category let's
Hi,
I personally like better the option A because it feels more natural and it is
more logical in that way that last rule is always overwriting previous rules.
Regards,
Zsolt
-Original Message-
From: development-bounces+zsolt.simon=nokia@qt-project.org
[mailto:development-bounces+z
On 03/01/2012 02:01 PM, ext wolfgang.b...@nokia.com wrote:
> I need to have a vote on a implementation detail regarding filtering
> of wildcards categories.
I vote for ordered handling because it's natural and consistent with
just about everything else out there.
--
Lincoln Ramsay - Senior Softw
Hi guys,
I need to have a vote on a implementation detail regarding filtering of
wildcards categories.
Let's say you have a category defined and a wildcard category as well.
A: Do you think the order in the configuration file plays an important rule or
B: If you set specific a category let's say
Sorry for top posting, but I just wanted to point out that the new Qt5 WebView
could also use both mouse and touch for more or less the same reasons you
stated for the terminal application. Actually mouse events should not be able
to cause a flick on the item (unless emulated for testing purpose
On Wednesday, February 29, 2012 12:08:19 PM ext Atlant Schmidt wrote:
> Shawn:
>
> This sounds like the roots of a strong proposal -- carry on!
>
> Two thoughts:
>
> o Please be sure your "pointing device" proposal
> can be generalized beyond "mice and touchscreens".
> There
Shawn:
This sounds like the roots of a strong proposal -- carry on!
Two thoughts:
o Please be sure your "pointing device" proposal
can be generalized beyond "mice and touchscreens".
There are certainly other pointing devices already
in the world (who remembers Light Pen
We've been chatting some more around the Oslo office about the fact that
even on platforms where the touchscreen is the primary pointing device,
both QWidgets and Qt Quick components are handling mostly mouse
events. In order to make that work, the Qt 4 approach (which is still
in place now) is for
2012/2/29 BRM :
> Just FYI - this is probably a better question for the qt-interests list as
> this list is focused on Qt5 at the moment (and post 5.0 after that).
I don't think it has something to do with Qt5 development sorry.
He posted at the right place. I answered to him but forgot to CC the
Just FYI - this is probably a better question for the qt-interests list as this
list is focused on Qt5 at the moment (and post 5.0 after that).
$0.02
BRM
>
> From: 陳敏華
>To: development@qt-project.org
>Sent: Tuesday, February 28, 2012 10:58 PM
>Subject: [Deve
> -Original Message-
> From: development-bounces+alex.blasche=nokia@qt-project.org
> On Tuesday 28 February 2012 10:07:51 Thiago Macieira wrote:
> > On terça-feira, 28 de fevereiro de 2012 09.01.52, Sean Harmer wrote:
> > > Hi,
> > >
> > > Are there any plans to move Qt Mobility unde
11 matches
Mail list logo