Hello,
I can't figure out what I'm doing wrong.
Any help would be appreciated.
I have attached an example but code is also below.
I try to set the example as Bottom Panel.
It is shown but it takes over the whole screen for its view strut
instead of just the height.
int main(int argc, char *argv[]
thanks. glad to hear that kwin wont rely on XDG_CURRENT_DESKTOP=KDE
default deco:
https://blog.qt.io/blog/2018/12/14/whats-new-wayland-platform-plugin-qt-5-12/
On Wed, Feb 27, 2019 at 4:09 PM David Edmundson
wrote:
>
> Kwin will decorate the window if and only if the client tells it to.
>
> Wit
Hello,
I don't know if this is the correct list to use (I subscribe to one
called k...@kde.org - the archives of it are empty).
I am trying a 'slim' wayland-session, I do see an issue, the session
starts this:
/usr/bin/kwin_wayland --xwayland --libinput konsole
It would get the default wayland
Hi,
maybe a Qt bug?
Using setType / setState (from kwindowsystem) on a custom qquickwindow
like here:
http://www.filedropper.com/testtar
results in the rendering to freeze.
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/
Hello list,
I went through the sources of kwindowsystem again as I want
to remove a previously set NET::KeepBelow property.
Is there such a thing in the api?
Also I noticed while running xprop on a window:
_NET_WM_ALLOWED_ACTIONS(ATOM) = _NET_WM_ACTION_CHANGE_DESKTOP,
_NET_WM_ACTION_ABOVE, _NET_W
ah ok, I got it :)
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
>no, if KWindowSystem implies SkipTaskbar if the window type is e.g. Splash the
>taskbar does not need any adjustments.
Sorry, maybe I'm misunderstanding :)
Does that mean that KWindowSystem adds SkipTaskbar to these windows?
If you have non KDE applications that don't have skipTaskbar set, but
do
>Given the high regression potential (windows which used to be included aren't
>shown any more - yes the one user's bug is the other user's feature) I would
>highly recommend to not change the behavior in 4.11.
Sure. I notice because for example xfce desktop and panel do not set
SkipTaskbar,
they r
KDE 4.11.5 as well as newer KDE's show the same behavior (couldn't
test Plasma 2 but I'm quite confident it applies also there).
The plasma plugins like taskbar do not respect NETWM_Type Property:
The plugins properly omit windows that have NETWM::SkipTaskbar set,
but as per netwm spec:
http://sta
And in case this was a hint I should contribute to a wayland
kwindowsystem backend, my c is awful, but I'm learning and believe I
will when I can. :)
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Yes, I absolutely will, I also have a wrapper that exposes
kwindosystem and kwindowinfo (and few netwm ones) functions to qml
https://github.com/damianatorrpm/qmltaskbar (used by
https://github.com/damianatorrpm/qmlpanel - old revision there,
uploading new one soon)
It is a complete rewrite of my
Ok.
>Whether closing a window is something which will be needed for Wayland in
>KWindowSystem is quite questionable. If at all it's the taskmanager, no other
>client should be allowed to perform such a task.
I hope you consider for the future non-plasma taskmanagers using
kwindowsystem (my fingers
I mean you read a property from one class and write to it in a differen class?
How can I use kwindowsystem to close a window in wayland (isn't
QX11Info::dispay required in netwm) ?
(don't get me wrong, I have great respect for your work and I do not
remotely understand the complexities like you do
I think that Thomas Luebking agrred with me on this:
http://osdir.com/ml/kde-devel/2014-02/msg00063.html
except closeWindow I also see missing
void setBlockingCompositing(bool active);
void setShowingDesktop(bool showing);
void setNumberOfDesktops(int numberOfDesktops);
It would be only natu
Hmm ok. If I come up with a better idea I'll let you know :)
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
It's ok if that behavior is for all wayland window manager's.
Every window manager supplies a list with known clients for the
copy/paste stack.
Maybe this is something that should be done as freedesktop standard
before it's too late...
___
Plasma-devel ma
> For Klipper this will happen for 5.1. Whether it's worth to keep klipper as a
> standalone application I'm not yet convinced, especially given that klipper
> will most likely be bound to KWin in a Wayland world.
Just ot of curiosity what part of Klipper would require kwin? If it's
for grabbing th
Thanks Martin for the answer.
>The long term plan for the strange parts like klipper and kmix is to transform
>them to a Plasmoid.
>
I hope this won't happen any time soon, I use them in not plasma
(their StatusNotifiers) :)
So general question: Should the StatusNotifier or the
StatusNotifierHos
Hi,
I implemented the StatusNotifier standard and I have one observation:
eg.
klipper: you left click it - it shows up - you click inside another
window - klipper hides
kmix & others - you left click it - it shows up - you click inside
another window - it stays until it's left clicked one more ti
Hello :)
Just some tiny (I hope) questions regarding the StatusNotifiers.
1) Is it expected that:
qdbus org.kde.StatusNotifierWatcher /StatusNotifierWatcher
org.kde.StatusNotifierWatcher.RegisteredStatusNotifierItems
returns org.kde.StatusNotifierItem-xx-y/StatusNotifierItem instead of
org.kd
And please make it possible to deactivate all usage of activities in
KF5. In KDE4 you can't even at compile time --disable-kactivities or
something. Of course one can say "don't use it". I don't. But one is
forced to see activities in every part of KDE. On the panel, on right
click on the desktop,
Hi all,
I'm writing a plasmoid (QML) that shows the application name and if
you hover on the plasmoid the application name turns into the
minimize, maximize, close button and the menubar.
I have it already working showing the application name and on hovering
showing the window buttons but I didn't
22 matches
Mail list logo
