On 06/27/2012 06:30 PM, ext marius.storm-ol...@nokia.com wrote:
> On 25/06/2012 13:44, ext Girish Ramakrishnan wrote:
>> Future plans
>> - Desktop OpenGL 3+ support, ES 3 support
>
> We've just added ANGLE support in Qt (-angle ), to enable DirectX
> usage instead of OpenGL ES 2 on Windows, due t
Everyone i know copy such small widgets in each application they develop...
As for WindowsMenu - on Mac it is built in designer form, you don't even
need to add it manually. IMHO, each multiple-window app needs it.
And what you suggest? To have QtWidgets and QtWidgets2 module? Why do we
need this
Op 27-6-2012 22:17, Иван Комиссаров schreef:
> Hm... What about adding new (maybe rather simple) widgets? QtCreator has
> QtColorButton class, QtFontButton, lineedit for editing shortcuts (i have my
> own modified copy).
> Browser example has ModelMenu and ModelToolBar classes (rather useful in s
Hm... What about adding new (maybe rather simple) widgets? QtCreator has
QtColorButton class, QtFontButton, lineedit for editing shortcuts (i have my
own modified copy).
Browser example has ModelMenu and ModelToolBar classes (rather useful in some
cases).
Recently, I implemented Windows menu (p
To use Qml on Win8 Metro, we must have a directX backend (with or without
angle .. but it seems that for now angle is directX9 only and Metro need
DX11), and to be able to use qt5 qml for digital signage on low end
hardware ( in that case qt5 qml is just perfect...) we need to have
hardware acceler
Hi!
On Wed, 27 Jun 2012, Thorbjørn Martsum wrote:
I do think that it would be a very good idea to have a QtWidget
maintainer. Not because Girish isn't a good approver (since he obviously
is) - but in order to ensure that people sees QtWidgets as alive. One of
the reasons people consider Qt Wi
On 27/06/2012 12:55, ext Thorbjørn Martsum wrote:
> Btw. Is somebody looking into the regressions in QGraphicsView?
Nope, QGV is currently lacking a maintainer.
Anyone with qualifications and feeling the urge? :)
--
.marius
___
Development mailing list
On Wednesday 27 June 2012 17:46:32 marius.storm-ol...@nokia.com wrote:
> On 27/06/2012 12:14, ext Sean Harmer wrote:
> > On Wednesday 27 June 2012 16:30:50 marius.storm-ol...@nokia.com
> >
> > wrote:
> >> On 25/06/2012 13:44, ext Girish Ramakrishnan wrote:
> >>> Future plans - Desktop OpenGL 3+ su
Thanks for the update. I just want to say 'hear hear' (or at "least Looks
good to me, but someone else must approve") ;)
I do think that it would be a *very good idea* to have a QtWidget
maintainer. Not because Girish isn't a good approver (since he obviously
is) - but in order to ensure that peop
On 27/06/2012 12:14, ext Sean Harmer wrote:
> On Wednesday 27 June 2012 16:30:50 marius.storm-ol...@nokia.com
> wrote:
>> On 25/06/2012 13:44, ext Girish Ramakrishnan wrote:
>>> Future plans - Desktop OpenGL 3+ support, ES 3 support
>>
>> We've just added ANGLE support in Qt (-angle ), to enable
>>
On Wednesday 27 June 2012 16:30:50 marius.storm-ol...@nokia.com wrote:
> On 25/06/2012 13:44, ext Girish Ramakrishnan wrote:
> > Future plans
> > - Desktop OpenGL 3+ support, ES 3 support
>
> We've just added ANGLE support in Qt (-angle ), to enable DirectX
> usage instead of OpenGL ES 2 on Window
On 25/06/2012 13:44, ext Girish Ramakrishnan wrote:
> Future plans
> - Desktop OpenGL 3+ support, ES 3 support
We've just added ANGLE support in Qt (-angle ), to enable DirectX
usage instead of OpenGL ES 2 on Windows, due to many buggy drivers.
How will this effort affect this usage?
Will we ac
Yes, that what's I mean. and I use *MSVC2010SP1 (from Windows SDK 7.1 +
VCSP1_update)*, on Windows 7 SP1 x64 or Windows 7 SP1 x86 both has the
problem.
2012/6/27 Joerg Bornemann
> On 26/06/2012 01:37, ext Loaden wrote:
>
> Of cause, It's only Qt5 issue. and only happened on Windows. (As I know
On 26/06/2012 01:37, ext Loaden wrote:
> Of cause, It's only Qt5 issue. and only happened on Windows. (As I know
> on Linux everything works well)
> See:
[...]
> If re-direct to some log, like this: "qbs platforms ls > output.log &&
> output.log", Then you can see what you want.
> Any comments?
S
I was requesting the same a good while back, but then decided that my
needs are better served by more QML-optimized class (QSIM is badly
stuck in QWidget mindset):
https://github.com/jnynas/QuickModel
https://github.com/jnynas/QuickModel/blob/master/quickmodel.h
Instead of QStandardItemModel, it
Hi,
> The relevant bug is https://bugreports.qt-project.org/browse/QTBUG-24456.
> For now, using dynamicRoles as Joona suggested should work around the problem.
thanks for pointing me to bug report and for providing the workaround!
Nils
___
Development
On Tuesday 26 June 2012 18:12:14 Stephen Kelly wrote:
> Hi there,
>
> I know it is late, but it was recently brought to my attention that
> QStandardItemModel could be moved from QtWidgets to QtGui, since QIcon was
> moved to QtGui.
>
> It seems that people doing model-view like to use QStandardI
On Wednesday, June 27, 2012 11:28:18 Thiago Macieira wrote:
> If you really, really, really want to install the two development
> environments in parallel, and considering that we already do need different
> prefixes, I'd say that the .so and .a files (if any) should be in
> $prefix/lib (e.g., /usr
On 26.06.2012 23:17, Olivier Goffart wrote:
>
> I'm not sure the class name is that important.
> I mean, if Foo().metaObject()->className() is just "Foo" it is still ok.
> Because it is hard to support, and hardly usefull.
OK, I thought className() is used by qobject_cast, but it isn't,
so it's m
On quarta-feira, 27 de junho de 2012 09.48.01, Jonathan Riddell wrote:
> As Thiago says it's pretty normal for libraries to keep the same names
> in different versions, the changed SONAME allows for the runtime bits
> both to be installed at the same time. It's the development files
> which can't
On Wed, Jun 27, 2012 at 10:17 AM, kim kulling
wrote:
> Good question, I have to doublecheck.
http://lists.qt-project.org/pipermail/development/2012-June/004431.html
Please make a patch release, if needed.
Best Regards,
Laszlo Papp
___
Development mail
Good question, I have to doublecheck.
Grettings
Kim Kulling
On Wed, Jun 27, 2012 at 11:02 AM, Laszlo Papp wrote:
> > I saw that Qt5 is using the Assimp-Library as a third party library for
> the
> > Q3d-part, right. I just want to let you know that we just released
> version
> > 3.0 for the nex
Top of the morning,
There is an infinite amount of insight on this list and a
complimentary infinite deficit in my noodle, so I thought I would put
it to the list:
building Qt with unsupported/linux-clang has worked gloriously (on
Linux) for most of the Qt 5 dev cycle although there was some
unpa
> I saw that Qt5 is using the Assimp-Library as a third party library for the
> Q3d-part, right. I just want to let you know that we just released version
> 3.0 for the next debian release. You can find it here:
Have you fixed the compilation issue with VS 2012 RC ? There was a
missing include...
On 27 June 2012 06:12, Girish Ramakrishnan wrote:
> My reasoning for renaming tools and libraries was relatively
> straightforward: They are not backward compatible and thus shouldn't
> be given the same since Qt4 and Qt5 will have to live together for a
> long time. Qt4 and Qt5 should be able to
Hi,
I saw that Qt5 is using the Assimp-Library as a third party library for the
Q3d-part, right. I just want to let you know that we just released version
3.0 for the next debian release. You can find it here:
https://sourceforge.net/projects/assimp/
https://sourceforge.net/projects/assimp/
We c
On terça-feira, 26 de junho de 2012 22.12.34, Girish Ramakrishnan wrote:
> My reasoning for renaming tools and libraries was relatively
> straightforward: They are not backward compatible and thus shouldn't
> be given the same since Qt4 and Qt5 will have to live together for a
> long time. Qt4 and
27 matches
Mail list logo
