This seems to be a complex issue - not as simple as the system being totally
unusable. Please see data in
https://bugreports.qt-project.org/browse/QTJIRA-172. Additional data from
other users would be welcomed. A new data sample will also be tested following
the JIRA upgrade today which will
Hi Mark,
In general: thanks for your efforts!
> In recent weeks, there have been some changes to JIRA with an aim towards
> lowering the barrier of access to the system.
There could be a better communication in the future. At least, I have
not been aware of those changes in the "background". Pe
On Tue, May 29, 2012 at 06:21:33AM +, ext mark.k...@nokia.com wrote:
> 2) The "Users" group (all logged in users) can now be assigned an
> issue. That means all >15.7K users in the system can be assigned an
> issue,
>
the immediate effect of this is that building that completion box now
takes
Hi,
I have hardware that requires me to allocate a different kind of surface
depending or whether or not OpenGL (RGB vs. BGR) is used. The usage of the
setSurfaceType() appears to be inconsistent though. E.g. EGLFS is the platform
plugin that calls this method on activation of the OpenGLContext, t
[snip]
> This builds a progressive enablement of system access.
> Anonymous - can see issues
> Users (Contributors) - can raise and comment on issues, see linked
> source code through Fisheye plugin and be assigned issues Current
> Assignee - can edit issues and progress them through the workflow
>
We will be taking bugreports.qt-project.org down for a couple of hours of
maintenance tomorrow, May 30, between 16:00 and 20:00 CEST.
The reason for the downtime is an important upgrade to Jira version 5.0.5.
An announcement will be sent out to the mailinglists when bugreports are
available aga
On Tue, May 29, 2012 at 10:52:30AM +0200, Knoll Lars (Nokia-MP/Oslo) wrote:
> On 5/29/12 8:22 AM, "ext Jørgen Lind" wrote:
>
> >Hi
> >> 6. Rename the handle() to platformXXX() since it's easy to educate
> >> that anything that has platform in it is out of reach of app
> >> developers.
> >> Status
>>
>> Question: How can we expose objects governed by QSharedPointer to QML
>> safely? I *can* guarantee the lifecycle beyond the life of my
>> QDeclarativeEngine.
>
> If you can guarantee that, then use mySharedPtr.data() as others have said.
Just a quick thought, would that suggesion be leading
On 5/29/12 8:22 AM, "ext Jørgen Lind" wrote:
>Hi
>> 6. Rename the handle() to platformXXX() since it's easy to educate
>> that anything that has platform in it is out of reach of app
>> developers.
>> Status: In progress, I am atm, marking handle() as obsolete and as an
>> alias to platformXXX().
Hi,
> 2. qwindowsysteminterface_qpa.h. This is a little tricky. We have
> qtestlib using it at this point because this is the way to send events
> to Qt. The API looks OK, can we make this public?
>
QWindowSystemInterface should not be public and is meant to be handled like the
other QPA headers.
Turunen Tuukka said:
> >>
> >> If feasible, I would like to see both Mac OS X 10.8 and Windows 8 (to
> >>the
> >> extent it is know at that time) working in the 4.8.3 release, as well as
> >> Ubuntu 12.04.
> >>
> >> In addition to making the obvious fixes it would be important to do
> >> regular
11 matches
Mail list logo
