There was a general agreement to add QGuiAction in a previous thread
on the dev list (Integrating QAction and the upcoming QML Action).
It's just that work on it hasn't started yet, if you want to
contribute you could see it done faster :) .
As for the API of QGuiAction I got the impression it was
Sorry for reanimating old thread:)
I was looking at QAction code and didn't see big dependecies on qtwidgets.
Isn't possible to implement this solution, keeping source and binary
compatibility:
We add QGuiAction to QtGui module. It has exact API like current QAction (which
is discussable, but
On Wednesday, July 04, 2012 08:22:06 lars.kn...@nokia.com wrote:
> * integration between a new action class and qaction doesn't require
> inheritance.
>
> * i believe this class can and should be developed together with QML
> components using it and with QAction interoperability in mind.
This wou
A few comments on the thread:
* a QAction like class is needed, and yes it could maybe even live in QtCore
* current Action is very tied to.widgets and i don't think splitting it up is a
good idea
* integration between a new action class and qaction doesn't require
inheritance.
* i believe t
Op 3-7-2012 18:31, Tomasz Siekierda schreef:
> Hi,
>
> just a quick note regarding this:
>
>> Would it not be possible to split QAction in two classes, just like
> QApplication was split? We could perhaps create a QCoreAction
>
> I think a better name would be QSimpleAction. Runs off the tongue a
>
Op 3-7-2012 18:45, simon.hausm...@nokia.com schreef:
> I'm not a fan of moving QAction back to QtGui, because there it would be a
> class that cannot be used by itself. Out of the box it is only useful with
> the containers in QtWidgets.
Why could it not be used by itself? I would totally use it
On Tuesday, July 03, 2012 20:55:45 lars.kn...@nokia.com wrote:
> Short note while on vacations... ;-)
>
> It was a conscious choice by me not to even try to split up QAction.
> QAction is very much bound to widgets and I am not convinced at all it's
> what we would need in QML.
>
> I think we wou
On Tuesday, July 03, 2012 16:45:06 simon.hausm...@nokia.com wrote:
> I'm not a fan of moving QAction back to QtGui, because there it would be a
> class that cannot be used by itself. Out of the box it is only useful with
> the containers in QtWidgets.
What do you mean by containers? You mean QMenu
Short note while on vacations... ;-)
It was a conscious choice by me not to even try to split up QAction.
QAction is very much bound to widgets and I am not convinced at all it's
what we would need in QML.
I think we would be better served in rethinking what is required for Qt
Quick and QML compo
I'm not a fan of moving QAction back to QtGui, because there it would be a
class that cannot be used by itself. Out of the box it is only useful with the
containers in QtWidgets.
I understand that you can theoretically use it just as property bag, but I
don't think that would be a common patter
Hi,
just a quick note regarding this:
> Would it not be possible to split QAction in two classes, just like
QApplication was split? We could perhaps create a QCoreAction
I think a better name would be QSimpleAction. Runs off the tongue a
bit more smoothly, plus the "Core" in the name will certai
>
> > How would you suggest solving it? QAction does have stuff like
> >
> > bool showStatusText(QWidget *widget=0);
> > QWidget *parentWidget() const;
> > QList associatedWidgets() const;
> > friend class QWidget;
> >
> > so it seems difficult to make it avoid depending on wid
Op 3-7-2012 15:07, Shawn Rutledge schreef:
> On Tuesday wk27 2012 July 03 09:36:26 AM ext Anselmo L. S. Melo wrote:
>> Hi,
>>
>> On 07/03/2012 05:06 AM, Davide Bettio wrote:
>>> Hello,
>>>
>>> I've noticed that QAction hasn't been moved from QtWidgets module to
>>> QtGui module, it would be really
On Tuesday wk27 2012 July 03 09:36:26 AM ext Anselmo L. S. Melo wrote:
> Hi,
>
> On 07/03/2012 05:06 AM, Davide Bettio wrote:
> > Hello,
> >
> > I've noticed that QAction hasn't been moved from QtWidgets module to
> > QtGui module, it would be really good if also that module gets moved
> > there.
Hi,
On 07/03/2012 05:06 AM, Davide Bettio wrote:
> Hello,
>
> I've noticed that QAction hasn't been moved from QtWidgets module to
> QtGui module, it would be really good if also that module gets moved
> there.
> QAction require QWidget for few things but I think that it is possible
> to so
Hello,
I've noticed that QAction hasn't been moved from QtWidgets module to
QtGui module, it would be really good if also that module gets moved
there.
QAction require QWidget for few things but I think that it is possible
to solve this problem easily.
If you give me some input on this topi
Hello,
I've noticed that QAction hasn't been moved from QtWidgets module to
QtGui module, it would be really good if also that module gets moved
there.
QAction require QWidget for few things but I think that it is possible
to solve this problem easily.
If you give me some input on this topi
17 matches
Mail list logo
