> -Original Message-
> Subject: Re: [Development] Fwd: Qt 5.3 Feature freeze is coming quite soon...
>
> [...]
> The problem with an add-on on the playground is the build system. Some
> people on Windows are complaining that they have to install Perl in order to
> compile.
Well, we could
Hi all,
There is new snapshot in
http://download.qt-project.org/snapshots/qt/5.2/5.2.1/2014-01-19_21/
Now there is all installers available, please verify your fixes
Qt5 changes in these packages:
https://codereview.qt-project.org/#change,75713:
* qtbase eaedc04...a198170 (45):
> Use non-threa
Jumping on this bandwagon late because I was away on vacation, but +1 from
me :-)
On Fri, Jan 10, 2014 at 6:24 AM, Knoll Lars wrote:
> Hi,
>
> I'd like to continue on filling gaps in our maintainer list and thus want
> to propose Simon Hausmann as the new maintainer for QtQml. Guess I don't
> n
Probably we may discuss it before make any unwanted bug reports...
Basically, I have the same problems described in the referenced topic from
URL. Specifically, I have a scene (tiles of geographic map) and an overlay
consisting of a polyline which should be editable via dragging its vertices.
By
Seem that loading from asset storage is really slow..
I am writing a QML application with around 15 QML files. The loading time
is 20 sec. I have tried to run profiler and take out many component to
speed up.
Finally , I found that just take out the statement "import ./widgets" can
reduce 10sec l
On 19 Jan 2014, at 14:18, iMath <2281570...@qq.com> wrote:
> when the widget is Activated or Deactivated ,QEvent::WindowActivate and
> QEvent::WindowDeactivate are not triggered
Please create a bug report at https://bugreports.qt-project.org.
> .
>
when the widget is Activated or Deactivated ,QEvent::WindowActivate and
QEvent::WindowDeactivate are not triggered .___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On 19 Jan 2014, at 12:26, Dmitrii Volosnykh wrote:
> My question is: should I report a new bug or add a comment to the old one?
You can make a new bug, describe the problem you have and we can discuss there.
Please post the bug report here.
FWIW I think the current behaviour is correct :-).
An
Much like an author of the message on stackoverflow (
http://stackoverflow.com/questions/2175503/qgraphicsview-accepted-events)
I'd like to be able to conditionally execute custom logic depending on the
accepted flag of the mouse event after default implementation of
QGraphicsView::mouseMoveEvent()
