Can anybody help me how to proceed in this case,
is #include "kalziumglwidget.moc" required in the .cpp file?
Although on including .moc and building gives
error-
Automoc for target compoundviewer
Generating kalziumglwidget.moc
/home/anu/kalzium/compoundviewer/kalziumglwidget.cpp:0: Note: No relev
On Fri, Jan 30, 2015 at 6:40 PM, Thomas Lübking
wrote:
> On Freitag, 30. Januar 2015 18:22:03 CEST, Vasily Khoruzhick wrote:
>
>> It's a way to keep all tray icons on the panel. In case of horizontal
>> panel
>> it's even seemless
>
>
> I'd not rather not expect a "seamless" result from this appro
On Freitag, 30. Januar 2015 18:22:03 CEST, Vasily Khoruzhick wrote:
It's a way to keep all tray icons on the panel. In case of horizontal panel
it's even seemless
I'd not rather not expect a "seamless" result from this approach.
You'll have an autopositioned/hiding wmsystemtray though, that's
On Fri, Jan 30, 2015 at 8:14 PM, Thomas Lübking
wrote:
> On Freitag, 30. Januar 2015 18:04:03 CEST, Martin Graesslin wrote:
Hi Thomas,
> What he suggests is to add a spacer into a panel and move a root parented
> XEmbed override_redirect container there.
> That's trivial enough (the spacer only
On Freitag, 30. Januar 2015 18:04:03 CEST, Martin Graesslin wrote:
Patches welcome. If you think it's important and that trivial you should be
able to do it, right?
What he suggests is to add a spacer into a panel and move a root parented
XEmbed override_redirect container there.
That's trivi
On Fri, Jan 30, 2015 at 8:04 PM, Martin Graesslin wrote:
Hi Martin,
> Patches welcome. If you think it's important and that trivial you should be
> able to do it, right?
Well, my area of expertise is embedded, kernel drivers and
bootloaders. But OK, I'll try to implement
a xembed tray widget. I
On Friday 30 January 2015 19:58:04 Vasily Khoruzhick wrote:
> On Fri, Jan 30, 2015 at 6:02 PM, Christoph Feck wrote:
> > On Friday 30 January 2015 11:41:42 Vasily Khoruzhick wrote:
> >> I've read [1] and [2] and as far as I understand, dropping xembed
> >> support was more political decision than
On Fri, Jan 30, 2015 at 6:02 PM, Christoph Feck wrote:
> On Friday 30 January 2015 11:41:42 Vasily Khoruzhick wrote:
>> I've read [1] and [2] and as far as I understand, dropping xembed
>> support was more political decision than technical difficulty.
Hi Christoph,
> I am sorry to say that you d
On Friday 30 January 2015 11:41:42 Vasily Khoruzhick wrote:
> I've read [1] and [2] and as far as I understand, dropping xembed
> support was more political decision than technical difficulty.
I am sorry to say that you did understand wrong. It was mostly a
technical decision. You are free to por
Hi,
I'd like to rise KDE backward compatibility issue once again.
I've read [1] and [2] and as far as I understand, dropping xembed
support was more political decision than technical difficulty. Please
kindly understand that breaking applications for users is a no-go.
I'd like to remind a situati
10 matches
Mail list logo
