On Wednesday, 2016-01-06, 23:33:32, Marco Martin wrote:
> On Wednesday 06 January 2016, Kai Uwe Broulik wrote:
> > Don't we handle the visible and enabled property of Action? That should
> > work for enabling / disabling certain drawer entries if in edit mode.
> > Irregardless of that usecase I wo
On Wed, Jan 06, 2016 at 03:08:02PM -0800, Dirk Hohndel wrote:
> On Wed, Jan 06, 2016 at 11:57:24PM +0100, Marco Martin wrote:
> > On Wednesday 06 January 2016, Dirk Hohndel wrote:
> > > If I write this as
> > >
> > > property list viewActions: [
> > > Action { }, Action { }
> > > ]
> > > prope
On Wed, Jan 06, 2016 at 11:57:24PM +0100, Marco Martin wrote:
> On Wednesday 06 January 2016, Dirk Hohndel wrote:
> > If I write this as
> >
> > property list viewActions: [
> > Action { }, Action { }
> > ]
> > property list editActions: [
> > Action { }, Action { }
> > ]
> >
> >
On Wednesday 06 January 2016, Dirk Hohndel wrote:
> If I write this as
>
> property list viewActions: [
> Action { }, Action { }
> ]
> property list editActions: [
> Action { }, Action { }
> ]
>
> it doesn't fail on syntax, but doesn't work. It always shows the
> viewActio
Let's move QAction to QtGui \o/ :(
> it belongs in Qt, even if they don't want it..
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
On Wednesday 06 January 2016, Kai Uwe Broulik wrote:
> > i just pushed the support of enabled.
>
> Awesome. However, considering the future of QtQuick Controls 1 and the fact
> that QQC 2 don't have an "Action" we should probably provide our own
> simple QObject for this. Once we sort out the dep
> i just pushed the support of enabled.
Awesome. However, considering the future of QtQuick Controls 1 and the fact
that QQC 2 don't have an "Action" we should probably provide our own simple
QObject for this. Once we sort out the deployment, that is. There will most
likely be additional prope
On Wed, Jan 06, 2016 at 11:31:58PM +0100, Kai Uwe Broulik wrote:
> Don't we handle the visible and enabled property of Action? That should work
> for enabling / disabling certain drawer entries if in edit mode.
> Irregardless of that usecase I would really expect that to work.
There is no "visi
On Wednesday 06 January 2016, Kai Uwe Broulik wrote:
> Don't we handle the visible and enabled property of Action? That should
> work for enabling / disabling certain drawer entries if in edit mode.
> Irregardless of that usecase I would really expect that to work.
i just pushed the support of en
Don't we handle the visible and enabled property of Action? That should work
for enabling / disabling certain drawer entries if in edit mode. Irregardless
of that usecase I would really expect that to work.
___
Plasma-devel mailing list
Plasma-devel
On Wed, Jan 06, 2016 at 01:49:28PM -0800, Dirk Hohndel wrote:
> On Wed, Jan 06, 2016 at 10:32:59PM +0100, Marco Martin wrote:
> > > > so, if it depends from pages, you just define a different
> > > > contextualactions list for every page definition...
> > >
> > > Currently we have one page that ha
On Wed, Jan 06, 2016 at 10:32:59PM +0100, Marco Martin wrote:
> > > so, if it depends from pages, you just define a different
> > > contextualactions list for every page definition...
> >
> > Currently we have one page that has two different states. You view a dive
> > or you edit a dive. Dependin
On Wednesday 06 January 2016, Dirk Hohndel wrote:
> > On Jan 6, 2016, at 12:47, Marco Martin wrote:
> >
> > On Wednesday 06 January 2016, Tomaz Canabrava wrote:
> >>> hmm, not sure it answers much yet.. who is mainDisplay?
> >>
> >> Its one of the Pages in an AplicationWindow, like the initialPa
> On Jan 6, 2016, at 12:47, Marco Martin wrote:
>
> On Wednesday 06 January 2016, Tomaz Canabrava wrote:
>>>
>>> hmm, not sure it answers much yet.. who is mainDisplay?
>>
>> Its one of the Pages in an AplicationWindow, like the initialPage.
>> the "current" one should give the Actions for th
On Wednesday 06 January 2016, Tomaz Canabrava wrote:
> >
> > hmm, not sure it answers much yet.. who is mainDisplay?
>
> Its one of the Pages in an AplicationWindow, like the initialPage.
> the "current" one should give the Actions for the contextDrawer.
so, if it depends from pages, you just de
On Wed, Jan 6, 2016 at 6:39 PM, Marco Martin wrote:
> On Wednesday 06 January 2016, Tomaz Canabrava wrote:
> > We need a menu that will change its contents based on whats being
> displayed
> > on the main part of the application.
> >
> > Something like:
> >
> > contextDrawer: MobileComponents.Con
On Wednesday 06 January 2016, Tomaz Canabrava wrote:
> We need a menu that will change its contents based on whats being displayed
> on the main part of the application.
>
> Something like:
>
> contextDrawer: MobileComponents.ContextDrawer {
> id: contextDrawer
> actions: mainDisplay.
On Wednesday 06 January 2016, Tomaz Canabrava wrote:
> We need a menu that will change its contents based on whats being displayed
> on the main part of the application.
>
> Something like:
>
> contextDrawer: MobileComponents.ContextDrawer {
> id: contextDrawer
> actions: mainDisplay.
On Wed, Jan 6, 2016 at 6:29 PM, Marco Martin wrote:
> On Wednesday 06 January 2016, Dirk Hohndel wrote:
> > I'm sure this email will mostly just expose my ignorance - but I'm OK
> with
> > that :-) -- I asked on IRC but I think no one was around who knew.
> >
> > I want to be able to change t
On Wednesday 06 January 2016, Dirk Hohndel wrote:
> I'm sure this email will mostly just expose my ignorance - but I'm OK with
> that :-) -- I asked on IRC but I think no one was around who knew.
>
> I want to be able to change the content of the context menu, depending on,
> err, context. See
20 matches
Mail list logo
