https://bugs.kde.org/show_bug.cgi?id=274931
--- Comment #69 from Arash B <ara...@gmail.com> --- @Martin Well then we go a step further out; some part of some api/interface (class constructor, public function, etc.) is used by others to signal to KWin that a window element should be created. Calling this api/interface part further leads to the creation a Client class instance, correct? Then add kwinWindowType to this api/interface part but give it a default value of UNKNOWN if the corresponding arg isn't passed on when the api/interface part is called. Then further pass on the value of kwinWindowType to the Client constructor (or Client::manage() which seems to serve instead of a constructor). -- You are receiving this mail because: You are watching all bug changes.
