Looking at the knock-on effects code-wise to other classes in QtBase of
changing QLocale to use ICU. Behavioural changes are not covered.
tl;dr?
* If we can port the QLocalePrivate number routines to call ICU instead of
their current implementations, the rest of Qt will "just work", except
QT
Splitting up some related issues into separate emails to make it easier for
people to address.
Which ICU version to use?
The latest ICU version is 4.8. See See http://site.icu-project.org/download
for detailed release notes.
OS X 10.6 shipped with ICU 4.0.
The earliest versios of major distr
On Monday 16 Jan 2012 23:13:39 Thiago Macieira wrote:
> I'd say that QLocale should return the information you need. If you need to
> display that, why shouldn't QLocale provide that info?
>
> *Setting* the info is, however, out-of-scope for Qt.
When I was discussing it with Denis at QtCS he was
ext-sami.1.rosend...@nokia.com said:
>
> Hi
>
> I am backporting fixes I have pushed to Qt5 to Qt4.8 now that 4.8 is
> available in gerrit. I got comments to my Qt4.8 patches that I should
> preferably cherry-pick the Qt5 commits to Qt4. I do not know how to set up my
> environment to enable t
On Tuesday, 17 de January de 2012 15.15.15, Giuseppe D'Angelo wrote:
> 2012/1/17 Thiago Macieira :
> > On Tuesday, 17 de January de 2012 02.43.33, Giuseppe D'Angelo wrote:
> >> 1) Support for more pattern options and match options. Right now you
> >> can see them commented in the .h (and there's no
Hi Morten,
On Tue, Jan 17, 2012 at 2:42 PM, wrote:
> QWheelEvent has fallen a bit behind and needs an update. It was once used for
> mouse wheel events only, but is today also used for scroll events generated
> from trackpad swipe gestures.
>
> There are two main issues:
>
> * QWheelEvents are
:-) In my defense I was surprised that it wasn't already reported so I
thought maybe I was doing something wrong. FWIW you can work around it for now
by putting the Text inside a Rectangle with clip: true.
BR,
Todd
> -Original Message-
> From: development-bounces+todd.rose=nokia@
On 17 January 2012 13:10, Charley Bay wrote:
>> > 3) Need a couple of better names for partial matching:
>> > - partial match preferring a complete match
>> > - partial match returning whatever match (partial or complete) is found
>> > first
>> >
>> > PCRE uses Soft and Hard respectively (which ar
2012/1/17 Thiago Macieira :
> On Tuesday, 17 de January de 2012 02.43.33, Giuseppe D'Angelo wrote:
>> 1) Support for more pattern options and match options. Right now you
>> can see them commented in the .h (and there's no code for them), but
>> adding them is trivial. Any opinions for just enablin
2012/1/17 Thiago Macieira :
> You have a method with two option flags:
> QRegularExpressionMatch match(const QString &subject,
> int offset = 0,
> MatchType matchType = NormalMatch,
>
Hi Pierre,
On Monday, January 16, 2012 10:57:28 AM ext Pierre Stirnweiss wrote:
> Hello everybody,
>
> As it is my first post in that list, a bit of presentation is due: my name
> is Pierre Stirnweiss, and I am part of the Calligra (www.calligra.org)
> team. I initially started coding in KOffice
On Tuesday, 17 de January de 2012 08.58.59, Simon Hausmann wrote:
> We are doing changes in qtbase, etc. for improved support of Qt 5 on
> Harmattan. I don't think it will make it to tier1 with just our effort, but
> we have a continued interest in running qtbase/qtdeclarative on Harmattan
> and i
QWheelEvent has fallen a bit behind and needs an update. It was once used for
mouse wheel events only, but is today also used for scroll events generated
from trackpad swipe gestures.
There are two main issues:
* QWheelEvents are either horizontal or vertical, requiring two events and two
cal
>
> > 3) Need a couple of better names for partial matching:
> > - partial match preferring a complete match
> > - partial match returning whatever match (partial or complete) is found
> > first
> >
> > PCRE uses Soft and Hard respectively (which are quite meaningless to
> > me).
>
> PreferComplete
On Tuesday, 17 de January de 2012 02.43.33, Giuseppe D'Angelo wrote:
> 1) Support for more pattern options and match options. Right now you
> can see them commented in the .h (and there's no code for them), but
> adding them is trivial. Any opinions for just enabling them or only
> some? In particu
On Tuesday, 17 de January de 2012 02.43.33, Giuseppe D'Angelo wrote:
> 2) Support for named capturing groups with duplicated names. The point
> is that this may require a couple of additional accessors inside
> QRegularExpressionMatch to extract all the substrings captured by a
> given name.
> The
On Tuesday, 17 de January de 2012 02.43.33, Giuseppe D'Angelo wrote:
> 3) Need a couple of better names for partial matching:
> - partial match preferring a complete match
> - partial match returning whatever match (partial or complete) is found
> first
>
> PCRE uses Soft and Hard respectively (whi
Hi,
we're working toward having a flexible yet simple API for window
orientations. It's important that the QWindow orientation API is
flexible enough to handle all use cases, whereas the APIs on top (in Qt
components for instance) can offer some more convenience for application
developers.
We
>
> 3) Need a couple of better names for partial matching:
> - partial match preferring a complete match
> - partial match returning whatever match (partial or complete) is found
> first
>
> PCRE uses Soft and Hard respectively (which are quite meaningless to
> me).
PreferCompleteMatch / PreferFir
On Tuesday, January 17, 2012 08:48:29 you wrote:
>
> Wouldn't that force the model to reset twice? That is, would I not
> have to add beginResetModel / endResetModel around the call to
> setRoleNames?
Yes, true. Also not an unsolvable problem.
In Qt5 it's not so relevant anyway because roleNames
On 1/17/12 11:14 AM, "Alan Alpert" wrote:
>Clipping has never been enabled by default (not even in QtQuick 1.x). An
>important detail he left out of the description (though not the example)
>was
>that he explicitly set clip: true on the Text element.
>
>This does make him seen extremely open min
Clipping has never been enabled by default (not even in QtQuick 1.x). An
important detail he left out of the description (though not the example) was
that he explicitly set clip: true on the Text element.
This does make him seen extremely open minded to consider clip: true not
clipping as a 'fe
Isn't this mostly because we don't cache text in textures anymore in Qt5?
Enabling clipping be default on all Text elements would cause a
performance hit, so I'm not sure this should be enabled by default.
Cheers,
Lars
On 1/17/12 7:30 AM, "ext andrew.den-ex...@nokia.com"
wrote:
>It¹s a bug. h
From: development-bounces+ext-sami.1.rosendahl=nokia@qt-project.org
[development-bounces+ext-sami.1.rosendahl=nokia@qt-project.org] on behalf
of Rosendahl Sami.1 (EXT-Reaktor/Helsinki)
Sent: Tuesday, January 17, 2012 10:35 AM
To: development@qt-project.org
Subject: [Development] Instructi
Hi
I am backporting fixes I have pushed to Qt5 to Qt4.8 now that 4.8 is available
in gerrit. I got comments to my Qt4.8 patches that I should preferably
cherry-pick the Qt5 commits to Qt4. I do not know how to set up my environment
to enable the cherry-picking because of the separate Qt5 and Qt
25 matches
Mail list logo
