https://bugs.kde.org/show_bug.cgi?id=274931
--- Comment #62 from Arash B <ara...@gmail.com> ---
@martin @tom
So this is my assessment of the situation: the border property is incorrectly
used to determine if a window should be placed on all activities, when in fact
other indicators should be used instead to make this assessment. This is
because using the border property will place certain windows (such as chrome)
on all activities when they shouldn't be.
I'm therefore trying to make a complete and distinct list of types of windows
that should be placed on all activities. I want to use this list to try to
create logic (in the code) that correctly determines if a window element should
be on all activities. I will create such logic on my own and then present them
in this thread for review and discussion, but someone else would have to
finally incorporate them in the software.
Here is a highly partial and vague start of the list of types of window
elements that should be placed in all activities when created:
* plasma extenders
* applet browser
* activity manager
Could you help me with two things? Firstly, could we complete this list by
adding all types of window elements that should be placed on all activities?
Secondly, could we make the list more granular by dividing each list item into
subcategories? For instance I'm thinking plasma extenders is a broad category
encompassing many different *types* of things. I don't need to know every
conceivable plasma extender that there's, but only relevant *types*.
If certain types of window elements require different method of procedures to
determine their type, then it would be very appreciated if they are mentioned
distinctively as a separate subcategory. For instance maybe a different set of
function calls has to be made to determine their type, while other functions
are used for other window element types.
I'm assuming each of these window elements of this list are represented by an
instance of the class KWin::Client, and that for all of them it is determined
in manage.cpp on line 234 by the following statement
...
if (Activities::self() && !isMapped && !noborder && isNormalWindow() &&
!activitiesDefined) {
...
Are these two assumptions correct? Or is it (possibly further) assessed
somewhere else whether if or not the window element should be placed on all
activities?
--
You are receiving this mail because:
You are watching all bug changes.
