On quinta-feira, 29 de março de 2012 23.31.38, Thiago Macieira wrote:
> Staged, re-staged, re-re-staged and once again for good measure, and it's
> in :-)
Oh, did I mention I had a QEXPECT_FAIL sneak in due to a feature that David
added to QUrl after I had already completed my work, and to fix tha
Suppose the URL:
file:///hash(%23)in path: ☺
which, after re-jigging, has:
path() == "/hash(#)in path: ☺";
and
path(QUrl::FullyEncoded) == "/hash(%23)in%20path:%20%E2%98%BA";
Question: can anyone come up with a valid use-case for
path(something here) == "/hash(%23
On quinta-feira, 29 de março de 2012 11.55.47, lars.kn...@nokia.com wrote:
> All is reviewed. Stage at your convenience ;-)
Staged, re-staged, re-re-staged and once again for good measure, and it's in
:-)
It took two more fixes applied on top -- license headers (some files were added
in September
QT_QPA_PLATFORM=windows:fontengine=native can't work now, -no-freetype is
invalid too?
Any comments?
2012/3/21 Loaden
> I found another way, just use configure option: *-no-freetype*
> The on Windows the issue gone.
>
> 2012/3/17 Loaden
>
>> Wow! Thanks!!
>> BTW, My fault, the vaule should be:
Hi, All, After try the current master, I found
*QT_QPA_PLATFORM*=*windows:fontengine=native
*don't work now, If set this env variable, will running failed on any qt
apps.
Then I try to re-configure with -no-freetype option.
And find in currently it can't work.
The font still not clear.
--
Regards
Hi Jordi,
great :-) Good News :-).
BTW:
I guess in Qt style it should be
bool tabVisible(int index) const;
void setTabVisible(int index, bool);
Thanks a lot and best Regards,
Carsten
Am 29.03.2012 14:29, schrieb Jordi Pujol:
> Hi Carsten,
>
> I'm working *right now* in the implem
On 29 March 2012 18:11, Robin Burchell wrote:
> On Mon, Mar 5, 2012 at 9:45 PM, Robin Burchell wrote:
>> I'd like to nominate Mark Brand (mabrand) for approver status.
>
> Three weeks after seconding and no objections, so Mark now has
> approver status. Congradulations!
Congrats!
--
Giuseppe D
On Mon, Mar 5, 2012 at 9:45 PM, Robin Burchell wrote:
> I'd like to nominate Mark Brand (mabrand) for approver status.
Three weeks after seconding and no objections, so Mark now has
approver status. Congradulations!
___
Development mailing list
Developm
On Thu, Mar 29, 2012 at 02:20:04PM +, ext shane.kea...@accenture.com wrote:
> It may not be trivial, but it's the workflow we have defined for promoting a
> playground module to an official add-on.
>
yeah. too bad our tool doesn't support that particularly well yet.
> Would it be any more com
On Wednesday, March 28, 2012 02:39:35 PM ext kai.koe...@nokia.com wrote:
> Hi there,
>
> In Qt 4 qDebug, qWarning etc just printed whatever was passed in. In Qt 5
> we've been changing this (1) so that you can configure Qt to print
> additional information by setting the QT_MESSAGE_PATTERN environ
On Thursday 29 March 2012 13:17:14 kai.koe...@nokia.com wrote:
> For my original proposal I took inspiration from the KDE debug output.
> Anyhow, I agree that the application name / pid just adds noise if you
> launched your app yourself from the shell.
>
> So, about "[%{type}] %{function} - %{me
On Thursday 29 March 2012 12:02:57 lars.kn...@nokia.com wrote:
> No, currently I do not want hundreds of feature branches on qtbase. We
> need to focus on stabilization and not doing new features.
With that logic you should also forbid other playground project.
___
It may not be trivial, but it's the workflow we have defined for promoting a
playground module to an official add-on.
Would it be any more complex than creating a new project (initialised with the
contents of the previous project repo, rather than empty) and deleting the old
project?
And we've
> -Original Message-
> From: Ramsay Lincoln (Nokia-MP/Brisbane)
> Sent: Thursday, March 29, 2012 9:20 AM
> To: Koehne Kai (Nokia-MP/Berlin)
> Cc: development@qt-project.org
> Subject: Re: [Development] Proposal: Changing the default output of
> qDebug and friends
>
> On 03/29/2012 05:03 P
On 03/29/2012 02:06 PM, ext Sergio Ahumada wrote:
> On 03/29/2012 01:59 PM, Knoll Lars (Nokia-MP/Oslo) wrote:
>> Approved. Sergio, can you help setting it up, please?
>>
>> Thanks,
>> Lars
>>
>
> So .. we'll go for a playground project instead of a branch ?
>
> I'll create playground/qlogger.git in
Hi Carsten,
I'm working *right now* in the implementation & test of 2 new methods
( I have to say Girish pointed me in the right direction ) :
bool isTabVisible(int index) const;
void setTabVisible(int index, bool);
I'm testing and still with minor painting problems, it looks fine. You
w
On Mar 29, 2012, at 2:18 PM, ext marius.storm-ol...@nokia.com wrote:
> Eh, after alpha please?
That will happen already (it's in the api_changes branch).
--
Bradley T. Hughes
bradley.hug...@nokia.com
___
Development mailing list
Development@qt-project
Eh, after alpha please?
--
.marius
> -Original Message-
> From: development-bounces+marius.storm-olsen=nokia.com@qt-
> project.org [mailto:development-bounces+marius.storm-
> olsen=nokia@qt-project.org] On Behalf Of Knoll Lars (Nokia-MP/Oslo)
> Sent: Thursday, March 29, 2012 6:56 AM
On 03/29/2012 01:59 PM, Knoll Lars (Nokia-MP/Oslo) wrote:
> Approved. Sergio, can you help setting it up, please?
>
> Thanks,
> Lars
>
So .. we'll go for a playground project instead of a branch ?
I'll create playground/qlogger.git in the afternoon
Cheers,
--
Sergio Ahumada
No, currently I do not want hundreds of feature branches on qtbase. We
need to focus on stabilization and not doing new features.
And if the people working on the logging FW want to release it to others
as an add-on to 5.0 why do you want to stop them?
Lars
On 3/29/12 11:18 AM, "ext Oswald Budde
Approved. Sergio, can you help setting it up, please?
Thanks,
Lars
On 3/29/12 2:50 AM, "ext wolfgang.b...@nokia.com"
wrote:
>Hi guys,
>
>I'm following the steps on
>http://wiki.qt-project.org/Creating_a_new_module_or_tool_for_Qt
>To get a playground project created for qlogger in place.
>
>qlog
All is reviewed. Stage at your convenience ;-)
Cheers,
Lars
On 3/28/12 11:42 PM, "ext Thiago Macieira"
wrote:
>On quarta-feira, 28 de março de 2012 19.08.04, lars.kn...@nokia.com wrote:
>> I'll try to go through them tonight.
>
>Thanks for the effort. I've gone over all the recommendations and
Hi Jordi,
thanks for the answer. Im looking forward to see
you changes in QT 5.1 :-).
Best Regards,
Carsten
Am 27.03.2012 07:51, schrieb Jordi Pujol:
> Sorry, answer sent only to Carsten ( my mistake... )
>
>> Afaik you only have the option to remove the tab . I've implemented
>> that fu
Hello everyone,
A while back, to go with the removal of file engines from public API, I
added a new function to QFileInfo [1] and there wasn't consensus on the
naming of this function. I offered to bring the name to the list for
review later and that is now.
bool QFileInfo::isNativePath() con
On Thu, Mar 29, 2012 at 12:50:21AM +, ext wolfgang.b...@nokia.com wrote:
> Because of the feature freeze we can't merge this patch into the trunk
> so we want to follow the way of the playground project.
>
this is a false dichotomy.
you want a feature branch for qtbase. created. sergio and/or
On Wednesday March 28 2012, Thiago Macieira wrote:
> - trivial default constructor ( = can be initialised by memset)
> - trivially copyable ( = memcpy creates independent object)
> [note: implies the next two]
> - movable ( = memcpy can be performed if the old object is discarded) -
> not a C
On 03/29/2012 05:03 PM, Koehne Kai (Nokia-MP/Berlin) wrote:
>> Why can't Creator just set the QT_MESSAGE_PATTERN environment
>> variable then and leave the default alone? Creator would not need
>> to show the filename and line number, just use them for when you
>> click on the warnings.
>
> You're
> -Original Message-
> From: development-bounces+kai.koehne=nokia@qt-project.org
> [mailto:development-bounces+kai.koehne=nokia@qt-project.org] On
> Behalf Of Ramsay Lincoln (Nokia-MP/Brisbane)
> Sent: Thursday, March 29, 2012 1:42 AM
> To: development@qt-project.org
> Subject: Re:
28 matches
Mail list logo
