2012/10/4 Rafael Roquetto
> Basically what you are doing is telling everyone there is no further
> discussion.
>
> My point is, it is not about leaving the users without the given changes.
> On
> the contrary, I even suggested that yet another super critical patch gets
> included (SSL), even thou
>Anyway, what is the plan right now? Don't do anything for the desktop
>components till Qt 5 is released then developing the desktop
>components further till they are perfect and ready to be released with
>Qt 5.1?
That is a reasonable proposal. Perhaps they could be an addon to Qt 5.0. To be
hon
First of all, which Qt version you're talking about?
I assume it is 4.8 since QAccessibleTextWidget has been reworked alot
in 5.0 and the problem you've described seems to gone there (see
QAccessibleTextWidget::characterRect() impl).
If it is 5.0, then you're probably subclassing the accessibility
On 4 October 2012 22:07, Laszlo Papp wrote:
> It seems to have been added few hours ago by "peppe":
> http://qt-project.org/wiki/diff/OnlineCommunities
Yes, sorry, I added the link and forgot to send an email here.
Hope that the link there addresses the situation somehow. Probably
more emphasis
It seems to have been added few hours ago by "peppe":
http://qt-project.org/wiki/diff/OnlineCommunities
By the way, you can probably do this next time yourself after logging in.
Laszlo
On Thu, Oct 4, 2012 at 10:02 PM, Laszlo Papp wrote:
>> http://qt-project.org/wiki/OnlineCommunities doesn't me
> http://qt-project.org/wiki/OnlineCommunities doesn't mention anything
> about mailing list either. Isn't mailing list a form of online
> community?
It is, and there is a mentioning there as well at the "Qt mailing lists" link.
Laszlo
___
Development m
> Sure. The question is, is that want the designer wants? What was the
> intent, and why?
>
> Do they want it 20mm because it looks good? Where? On a hand-held device? On
> a desktop? On a projector? Is 20mm because they want to guarantee an easy
> touch target? Or easy to see from a particular
Hello,
I am trying to fix tst_QAccessibility for QNX, and I have a problem on line
2750:
QCOMPARE(iface->textInterface()->characterRect(0,
QAccessible2::RelativeToParent).size(), QSize(fm.width("h"), fm.height()));
This comparison is failing, because the caracter rect height is bigger than
the h
> -Original Message-
> From: Shawn Rutledge [mailto:shawn.t.rutle...@gmail.com]
> Sent: Thursday, October 04, 2012 11:09 AM
> To: Tony Van Eerd
> Cc: development@qt-project.org
> Subject: Re: [Development] resolution independence (was Re: Retina
> display support)
>
> On 4 October 2012 16:
Hi,
On 10/04/2012 05:21 PM, Stephen Kelly wrote:
> On Thursday, October 04, 2012 17:06:08 Eskil Abrahamsen Blomfeldt wrote:
>> If
>> you are working on changes to the qtdoc repository, could you please
>> move it over to "newdocs" branch so we can minimize conflicts?
>
> Excuse my circular logic,
On Thursday, October 04, 2012 17:06:08 Eskil Abrahamsen Blomfeldt wrote:
> If
> you are working on changes to the qtdoc repository, could you please
> move it over to "newdocs" branch so we can minimize conflicts?
Excuse my circular logic, but if everyone should commit to newdocs and no one
sho
On 4 October 2012 16:27, Tony Van Eerd wrote:
> I think proper resolution dependence and independence requires, at times at
> least, 2 separate measurements for each widget:
>
> visual measure:
> - physical measurement is in arcminutes (ie angle between
> for the smallest dot you can se
Hi,
To avoid disrupting the current release process, we in the documentation
clean-up project here in Oslo have made the branch "newdocs" in the
qtdoc repository, where we are currently doing some overhauls,
especially to the structure of the Qt documentation.
There will be a lot more informat
On Thursday, October 04, 2012 13:46:06 Pasion Jerome wrote:
> Hello,
>
> We have this page: http://doc-snapshot.qt-project.org/5.0/modules.html
> There are links that need to be updated (waiting for some merges first), but
> for the most part, it lists all of the Qt 5 modules. If I get a list of t
On Thu, Oct 04, 2012 at 01:11:19PM +, Turunen Tuukka wrote:
>
>
> My preference is towards releasing now and making proper 4.8.4 (with more
> content) later. It is true that getting the security fix in is also
> valuable and then we certainly need to call it 4.8.4.
And what do you think abou
Hi,
I have suggested this to the web team back in Nokia days, but it
unfortunately never happen (never got any response).
The problem is, after qt-project.org redesign, there is simply not
link to lists.qt-project.org at all, not a single word about the
existence of a mailing list. The wiki link
I think proper resolution dependence and independence requires, at times at
least, 2 separate measurements for each widget:
visual measure:
- physical measurement is in arcminutes (ie angle between for the smallest dot you can see - ie discerning the
last line of an eye chart)
Hello,
We have this page: http://doc-snapshot.qt-project.org/5.0/modules.html
There are links that need to be updated (waiting for some merges first), but
for the most part, it lists all of the Qt 5 modules. If I get a list of the
released modules, I can modify that page.
What about the modules
On quinta-feira, 4 de outubro de 2012 06.14.05, Thiago Macieira wrote:
> All the modules in the Qt Essentials package have approval by the Chief
> Maintainer[*] to be released as Qt 5.0:
> all modules in the qtbase repository
> Qt Quick 1 and Qt Quick 2
> Qt WebKit
>
Hello
In the release team, we looked at what we want to release with Qt 5 and came
to the conclusion we need explicit approval.
All the modules in the Qt Essentials package have approval by the Chief
Maintainer[*] to be released as Qt 5.0:
all modules in the qtbase repository
Qt
On 4.10.2012 16.02, "Rafael Roquetto" wrote:
>Basically what you are doing is telling everyone there is no further
>discussion.
That is incorrect. What I said is that we can either release 4.8.3-1 now
as the installers are ready, or make adjustments and release later.
My preference is towards
Basically what you are doing is telling everyone there is no further
discussion.
My point is, it is not about leaving the users without the given changes. On
the contrary, I even suggested that yet another super critical patch gets
included (SSL), even though this means we are deviating from the s
On quinta-feira, 4 de outubro de 2012 12.31.00, Turunen Tuukka wrote:
> Ok, back to the options.
>
> We can issue 4.8.3-1 now with the copyright change and MinGW fix, no other
> fixes in. These packages are ready and tested for both open-source and
> commercial licensees.
I don't like that. If it
On quinta-feira, 4 de outubro de 2012 13.38.46, Stephen Kelly wrote:
> git merge v4.8.4
Better yet:
git merge -s ours v4.8.4
No conflicts.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digital
Ok, back to the options.
We can issue 4.8.3-1 now with the copyright change and MinGW fix, no other
fixes in. These packages are ready and tested for both open-source and
commercial licensees.
Or we can provide this only for the commercial licensees, if you really
think that the Qt Project shoul
On Thu, Oct 04, 2012 at 11:53:48AM +, Turunen Tuukka wrote:
>
> Naturally everything can be done, it is just a matter how much work it
> takes. It is easy to talk if it not you who is doing it...
>
> It has already been decided to start using branches, so later on things
> like this will get
Hi,
By now the pros and cons of the two approaches ("free scaling" vs. "2x") have
been well argued by Rutledge and Ziller; I'll go on an present the patches.
These implement the 2x type of high-dpi support.
In short, there is now an distinction between points and pixels. Window, widget
and eve
On 4.10.2012 14.55, "shane.kea...@accenture.com"
wrote:
>> I see three critical things which must be released asap:
>>
>> 1. the (C) headers change
>> 2. MingW patch.
>> 3. d41dc3e101a694dec98d7bbb582d428d209e5401 - this is the SSL
>> workaround from Robin.
>>
>(Rich, not Robin)
>
>If the releas
On Thu, Oct 04, 2012 at 11:55:23AM +, shane.kea...@accenture.com wrote:
> (Rich, not Robin)
My bad, sorry Rich.
>
> If the release is called 4.8.4, then the SSL security patch must be included,
> as we said 4.8.4 would include this in the security announcement.
>
> Subject to local law, comm
On 4.10.2012 14.38, "Stephen Kelly" wrote:
>On Thursday, October 04, 2012 06:27:58 Turunen Tuukka wrote:
>>
>> Then we have more time to change the copyrights to the older
>> versions, and can still have the installers available for the users.
>
>You mean you're going to change the copyright not
> I see three critical things which must be released asap:
>
> 1. the (C) headers change
> 2. MingW patch.
> 3. d41dc3e101a694dec98d7bbb582d428d209e5401 - this is the SSL
> workaround from Robin.
>
(Rich, not Robin)
If the release is called 4.8.4, then the SSL security patch must be included,
as
On 4.10.2012 14.20, "Stephen Kelly" wrote:
>On Wednesday, October 03, 2012 19:00:14 Turunen Tuukka wrote:
>> >>> Can't you push a commit on top of 4.8.3 that updates the license
>> >>> files, and tag that commit 4.8.3-1?
>> >>
>> >> If we do that, we should just call it 4.8.4.
>> >
>> > Isn't
On Thu, Oct 04, 2012 at 06:27:58AM +, Turunen Tuukka wrote:
>
>
> Unfortunately release branches have not been used in the Qt Project - we
> have made all 4.8.x releases directly from the 4.8 branch. That is the
> root cause of many problems in releasing and an issue that will be
> addressed
On Thursday, October 04, 2012 06:27:58 Turunen Tuukka wrote:
> On 4.10.2012 0.15, "Rafael Roquetto" wrote:
> >What's the problem of "branching" 4.8.3, cherry-picking
> >619136931e2c985377348d196d488e429a4858d6 (is that the right patch?), and
> >tagging it as 4.8.4?
>
> Unfortunately release branc
On Wednesday, October 03, 2012 19:00:14 Turunen Tuukka wrote:
> >>> Can't you push a commit on top of 4.8.3 that updates the license
> >>> files, and tag that commit 4.8.3-1?
> >>
> >> If we do that, we should just call it 4.8.4.
> >
> > Isn't that what happened also when Nokia bought Qt? 4.4.3 w
Hi everybody,
I have the following issue with the SceneGraph and QQuickItem.
I call the update() of my QQuickItem class from a worker thread instead of the
main thread. There I get sometimes the assert warning, that prevDirtyItem is a
Null pointer. I looked it up in the source code (qquickitem.c
uhhh oops, my mistake. Forget about this topic :)
On Thu, Oct 4, 2012 at 12:36 PM, Sivan Greenberg wrote:
> IIRC, this was supported long ago and is the basis for the extreme
> reuse QML enables.
>
> -Sivan
>
> On Thu, Oct 4, 2012 at 12:27 PM, Tomasz Siekierda wrote:
>>> What i really miss in QM
IIRC, this was supported long ago and is the basis for the extreme
reuse QML enables.
-Sivan
On Thu, Oct 4, 2012 at 12:27 PM, Tomasz Siekierda wrote:
>> What i really miss in QML is the ability to let a component inherit
>> functionality from another component.
>
> This is already a feature: jus
This discussion shows another problem.
ATM it is not possible to release a Qt4 version
(has Qt5 the same problem?) with a proper version
number based on an already released version and
containing only some patches.
This is not only a scenario when the Qt copyright
changes. It could happen all the
> What i really miss in QML is the ability to let a component inherit
functionality from another component.
This is already a feature: just create your components in separate files
and use this:
// BaseButton.qml
Item
{
property int someNum: 100
... the basics for a button.
}
// SpecialBut
On Thursday, October 04, 2012 10:36:59 AM Mark wrote:
> Hi,
>
> The principle is simple. I'd like to be able to make a base component
> and create different implementations of it. What i really miss in QML
> is the ability to let a component inherit functionality from another
> component.
> For ex
On 1 Oct 2012, at 11:57, Rutledge Shawn wrote:
> On Sep 21, 2012 w38, at 10:37 AM, ext Ziller Eike wrote:
>>
but that would be a huge waste of system resource and performance drag
when running on non-retina system. Are there any better solutions?
>>>
>>> Aren't you seeing the window
I do not think there is any direct focus on the Qt Components right
now by Digia, Canonical, KDE and forth.
Note that, it is not just about the desktop components, but even the
mobile components. See my previous unreplied query here just for an
instance:
http://lists.qt-project.org/pipermail/qt-co
On Wed, Oct 3, 2012 at 1:31 PM, Bache-Wiig Jens
wrote:
> No worries. Development is still going strong. It just happens that the
> people that are involved in component development are the very same people
> trying to push a Qt 5.0 release out of the door right now. This obviously
> means a bit
Hi,
The principle is simple. I'd like to be able to make a base component
and create different implementations of it. What i really miss in QML
is the ability to let a component inherit functionality from another
component.
For example the following where we have a base button with different
featu
45 matches
Mail list logo
