On Wednesday 16 January 2013 09:41:08 Weng Xuetian wrote:
> On Wednesday 16 January 2013 11:08:57，Martin Gräßlin :
> > 0:14 Marco Martin wrote:
> > > On Wednesday 16 January 2013, Martin Gräßlin wrote:
> > > > > at least for 4.10 you can maybe force translucent to dialogs.
> > > > > there is only o
On Wednesday 16 January 2013 11:08:57，Martin Gräßlin :
> 0:14 Marco Martin wrote:
> > On Wednesday 16 January 2013, Martin Gräßlin wrote:
> > > > at least for 4.10 you can maybe force translucent to dialogs.
> > > > there is only one version of widgets/background, so should be always
> > > > ok-ish
On Wednesday 16 January 2013 11:00:14 Marco Martin wrote:
> On Wednesday 16 January 2013, Martin Gräßlin wrote:
> > > at least for 4.10 you can maybe force translucent to dialogs.
> > > there is only one version of widgets/background, so should be always
> > > ok-ish (can never be used as a main fr
On Wednesday 16 January 2013, Martin Gräßlin wrote:
> > at least for 4.10 you can maybe force translucent to dialogs.
> > there is only one version of widgets/background, so should be always
> > ok-ish (can never be used as a main frame of a window tough since
> > doesn't have an opaque version)
>
On Wednesday 16 January 2013 10:28:30 Marco Martin wrote:
> On Wednesday 16 January 2013, Martin Gräßlin wrote:
> > * EffectFrames render a "widgets/background"
> > * PresentWindows and DesktopGrid render a "dialogs/background"
> > * TabBox uses PlasmaCore.FrameSvgItem with "dialogs/background"
> >
On Wednesday 16 January 2013, Martin Gräßlin wrote:
> * EffectFrames render a "widgets/background"
> * PresentWindows and DesktopGrid render a "dialogs/background"
> * TabBox uses PlasmaCore.FrameSvgItem with "dialogs/background"
> * DesktopChangeOSD uses PlasmaCore.Dialog, so implicitly
> "dialogs
