[kwin] [Bug 449503] My Laptop in 'Panic State' when disengaged from the docking station/VGA port disconnected ... Laptop unusable, if 'Windows Effect' disabled laptop usable without the eye candy
https://bugs.kde.org/show_bug.cgi?id=449503 aiamuzz changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- --- Comment #2 from aiamuzz --- (In reply to Nate Graham from comment #1) > This is thankfully fixed in Plasma 5.24 already. @Nate Graham ... I am not using plasma directly, however i am using Linux Deepin which has kwin ... Where does that leave me ... can i run some standalone upgraded package to append my current setup ? thank.s -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449503] My Laptop in 'Panic State' when disengaged from the docking station/VGA port disconnected ... Laptop unusable, if 'Windows Effect' disabled laptop usable without the eye candy
https://bugs.kde.org/show_bug.cgi?id=449503 --- Comment #4 from aiamuzz --- (In reply to Nate Graham from comment #3) > You can indeed. can you please provide a link to such a package / patch that can fix my issue ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449503] My Laptop in 'Panic State' when disengaged from the docking station/VGA port disconnected ... Laptop unusable, if 'Windows Effect' disabled laptop usable without the eye candy
https://bugs.kde.org/show_bug.cgi?id=449503 aiamuzz changed: What|Removed |Added CC||muzafsh@gmail.com --- Comment #7 from aiamuzz --- @nate Graham ... please respond to @Zeno for he is from Deepin Linux team and is seeking patches so the same can be merged into their current kwin version. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448778] Unplugging an external monitor leads to a crash
https://bugs.kde.org/show_bug.cgi?id=448778 aiamuzz changed: What|Removed |Added Resolution|FIXED |--- Component|platform-drm|multi-screen Ever confirmed|0 |1 CC||muzafsh@gmail.com Status|RESOLVED|REOPENED Platform|Archlinux |Debian stable --- Comment #17 from aiamuzz --- Hello @Zamundaaa, SOFTWARE/OS VERSIONS OS : Linux Deepin(Debian based) KERNEL: 5.15.45-amd64-desktop KWIN: kwin 5.15.5 Seems like even i am facing the same issue, from a pretty long time that too ... STEPS TO REPRODUCE 1. Log into the laptop with an external monitor attached 2. Works fine when external monitor is attached 3. Unplug monitor/dock(with monitor attached) 4. grey screen with only the cursor showing on the laptop screen cursor responds but crashed screen. OBSERVED RESULT Kwin crashes with only a grey screen with only the mouse cursor visible which responds fine when moved but the screen is unresponsive. a perpetual state until the monitor/dock is reconnected. My situation is so bad that I have to CONNECT an external monitor or atleast the VGA port to my laptop to get it come back from the freeze. STRANGELY THOUGH WHEN I TURN 'WINDOWS EFFECT' OFF THEN THE LAPTOP IS USABLE WITH THE UGLY UI OF COURSE, FOR WINDOWS EFFECT IS THE REAL UX WITHOUT WHICH IT LIKE TRAVELLING IN A CARRIAGE IN THE AGE OF SPACE TRAVEL. EXPECTED RESULT It doesn't crash ON DISCONNECTING THE EXTERNAL MONITOR OR DOCKING STATION. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448778] Unplugging an external monitor leads to a crash
https://bugs.kde.org/show_bug.cgi?id=448778 --- Comment #18 from aiamuzz --- @zamundaaa, I will open another bug if you so wish, but the symptoms are the same as reported by @Matej Mrenica. (as replied by Matej Mrenica from comment #8) > In the log I provided I unplug the cable before 08:52:41, is that what you > are asking? After that only a cursor appears on my laptop screen ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448778] Unplugging an external monitor leads to a crash
https://bugs.kde.org/show_bug.cgi?id=448778 --- Comment #20 from aiamuzz --- (In reply to Zamundaaa from comment #19) > (In reply to aiamuzz from comment #18) > > @zamundaaa, I will open another bug if you so wish, but the symptoms are the > > same as reported by @Matej Mrenica. > > Can you test if it happens on Wayland as well? > Also, can you test if it happens with a newer version of KWin? Or is 5.15.5 > a typo? It's been unsupported for more than three years now. I know, I've heard that its 3 years old, unfortunately its true Linux Deepin are lagging way behind ... > Can you test if it happens on Wayland as well ? I am sorry I am just a Linux power user with limited understanding, so i'll not know the answer to that question. If you have some commands whose outputs you want, I can run them so you can help diagnose the issue i am facing. It would sound amusing, But i have basically pulled a VGA Cable from an old CRT monitor along with the PCB its connected to and i kind of attach this dangling cable with the PCB to my laptop to get my laptop working with 'Windows Effect' enabled ... the alternative being turning off 'Windows Effect' and using an ugly interface ... with the choice between a deep sea and the devil, i've chosen a dangling cable at my office as am used to the features 'Windows Effect' has to offer. FYI ... https://github.com/linuxdeepin/deepin-kwin ... this is the repo of the package that's probably running on my system. I was just hoping you are able to identify the issue i am facing and raise a MR/PR to this repo with the patch/code correction so i can install it and rectify my problem. Please let me know the set of commands you want me to run on my affected system. Thanks for the quick and prompt response. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448778] Unplugging an external monitor leads to a crash
https://bugs.kde.org/show_bug.cgi?id=448778 --- Comment #21 from aiamuzz --- I notice the following ... Extended monitor ... Resolution : 1920 x 1080 (Recommended) Refresh Rate : 60Hz (Recommended) Laptop Screen ... Resolution : 1920 x 1080 (Recommended) Refresh Rate : 60.01Hz (Recommended) I have a feeling the fix you offered here to @Matej Mrenica might fix my problem as well ... as i see in your comment 9 you've spoken of refresh rates of 6 and 60001 ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448778] Unplugging an external monitor leads to a crash
https://bugs.kde.org/show_bug.cgi?id=448778 --- Comment #23 from aiamuzz --- (In reply to Zamundaaa from comment #22) > Yes, that looks like the same underlying problem, no further testing is > needed. We don't support such old versions and especially not forks of them > though. > > The things you can do is to ask the Deepin maintainers to update their fork > of KWin to include an equivalent of > https://invent.kde.org/plasma/kwin/-/commit/ > 9f9ad7036518f0d0df984a3eda28e2b4c57607d3, or switch to a distro that offers > an upstream version of KWin 5.24 or newer. oh ... thanks for the confirmation. unfortunately they are proceeding at snails pace ... the only hope is that they may have picked up the latest kwin version in their next years release. @Zamundaaa ... i was hoping to ask a favor ... the following is the version package whose fork my distro may have relied on. https://invent.kde.org/plasma/kwin/-/archive/v5.15.5/kwin-v5.15.5.zip I see that the folder and file structure is way different to the latest version, which is expected given the above is 3 years old. If its possible i was hoping you could point me too the file that has the equivalent of the refreshRate line implementation ... props->refreshRate = mode["refresh"].toDouble() * 1000; I was hoping, as its only one word 'round ()' to be modified ... i though i could initiate the pull request on my distro forked repo. I have been trying since the last couple of days with regard to 'src' folder and a file named 'drm_backend.cpp' but with no luck, of course its understandable the code would have undergone considerable change in structure and implementation in the last 3 years. hoping for a helping hand ... thanks for identifying and confirming the posssible issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448778] Unplugging an external monitor leads to a crash
https://bugs.kde.org/show_bug.cgi?id=448778
--- Comment #24 from aiamuzz ---
apologies for trying to be self reliant ... I am the only one facing this
issues it seems ... so trying to help myself ...
could these be the possible file that needs the corrected code ?
kwin-v5.15.5/plugins/platforms/drm/drm_output.cpp
relevant parts ???
**
namespace {
quint64 refreshRateForMode(_drmModeModeInfo *m)
{
// Calculate higher precision (mHz) refresh rate
// logic based on Weston, see compositor-drm.c
quint64 refreshRate = (m->clock * 100LL / m->htotal + m->vtotal / 2) /
m->vtotal;
if (m->flags & DRM_MODE_FLAG_INTERLACE) {
refreshRate *= 2;
}
if (m->flags & DRM_MODE_FLAG_DBLSCAN) {
refreshRate /= 2;
}
if (m->vscan > 1) {
refreshRate /= m->vscan;
}
return refreshRate;
}
}
**
// read in mode information
QVector modes;
for (int i = 0; i < connector->count_modes; ++i) {
// TODO: in AMS here we could read and store for later every mode's
blob_id
// would simplify isCurrentMode(..) and presentAtomically(..) in case
of mode set
auto *m = &connector->modes[i];
KWayland::Server::OutputDeviceInterface::ModeFlags deviceflags;
if (isCurrentMode(m)) {
deviceflags |=
KWayland::Server::OutputDeviceInterface::ModeFlag::Current;
}
if (m->type & DRM_MODE_TYPE_PREFERRED) {
deviceflags |=
KWayland::Server::OutputDeviceInterface::ModeFlag::Preferred;
}
KWayland::Server::OutputDeviceInterface::Mode mode;
mode.id = i;
mode.size = QSize(m->hdisplay, m->vdisplay);
mode.flags = deviceflags;
mode.refreshRate = refreshRateForMode(m);
modes << mode;
}
**
void DrmOutput::setWaylandMode()
{
AbstractOutput::setWaylandMode(QSize(m_mode.hdisplay, m_mode.vdisplay),
refreshRateForMode(&m_mode));
}
**
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 448778] Unplugging an external monitor leads to a crash
https://bugs.kde.org/show_bug.cgi?id=448778 --- Comment #25 from aiamuzz --- oh ok ... seems like the exact same file ... "drm_backend.cpp" ... the implementation however seems quite different to the one you have in the latest version. *** //2.init wayland output device QString name = "VGA-1"; QString model = "VGA-1000-unknown"; QString manufacturer = "UOS"; QByteArray uuid = "ff"; QVector modes; KWayland::Server::OutputDeviceInterface::Mode dmode; dmode.id = 0; dmode.size = QSize(mode.hdisplay, mode.vdisplay); dmode.flags = KWayland::Server::OutputDeviceInterface::ModeFlag::Current; dmode.refreshRate = mode.vrefresh * 1000LL; modes << dmode; output->initWaylandOutputDevice(name, model, manufacturer, uuid, modes); ** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448778] Unplugging an external monitor leads to a crash
https://bugs.kde.org/show_bug.cgi?id=448778 --- Comment #26 from aiamuzz --- I know at the risk of sounding foolish ... will this do the trick ? your MR ... for the latest version - props->refreshRate = mode["refresh"].toDouble() * 1000; + props->refreshRate = round(mode["refresh"].toDouble() * 1000); will the following do the trick to the 3 yr old version ? - dmode.refreshRate = mode.vrefresh * 1000LL; + dmode.refreshRate = round(mode.vrefresh * 1000LL); "A better fix would be to use integers instead of floating point numbers" i don't see toDouble(floating point number) implementation in the above line of code as seen in the implementation of the latest versions ... I am guessing it may need some more tinkering with the code in files preceding "drm_backends.cpp" h ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448778] Unplugging an external monitor leads to a crash
https://bugs.kde.org/show_bug.cgi?id=448778 --- Comment #27 from aiamuzz --- I am guessing my fix lies in the following 3 files ... understanding code and what it does is way above my paygrade ... https://github.com/linuxdeepin/deepin-kwin/blob/master/plugins/platforms/drm/screens_drm.cpp https://github.com/linuxdeepin/deepin-kwin/blob/master/plugins/platforms/drm/drm_backend.cpp https://github.com/linuxdeepin/deepin-kwin/blob/master/plugins/platforms/drm/drm_output.cpp @Zamundaaa ... nothing important ... i don't see your MR (https://invent.kde.org/plasma/kwin/-/commit/9f9ad7036518f0d0df984a3eda28e2b4c57607d3) synced into the kwin repo on github (https://github.com/KDE/kwin/blob/master/src/backends/drm/drm_backend.cpp) ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449503] New: My Laptop in 'Panic State' when disengaged from the docking station/VGA port disconnected ... Laptop unusable, if 'Windows Effect' disabled laptop usable without the eye candy
https://bugs.kde.org/show_bug.cgi?id=449503 Bug ID: 449503 Summary: My Laptop in 'Panic State' when disengaged from the docking station/VGA port disconnected ... Laptop unusable, if 'Windows Effect' disabled laptop usable without the eye candy Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: muzafsh@gmail.com Target Milestone: --- SUMMARY *** My Laptop in 'Panic State' when disengaged from the docking station/VGA port disconnected ... Laptop unusable, if 'Windows Effect' disabled laptop usable without the eye candy *** STEPS TO REPRODUCE I don't know if there are any specific steps here that i can list out. It is just that the laptop works great with all the eye candy windows effects when its connected to an external monitor or when its docked to my docking station. Hell breaks loose when i disengage the docking station or pull out the VGA cord of the external monitor. after that everything comes to a standstill, no amount of efforts to salvage the system to get it to respond and make it usable are futile. The sad part is that even a hard shutdown and restart does not restore defaults, it seems like some config settings are unaffected by the shutdown and restart. The only thing that seems to work is if i disable the 'Windows Effect', when this setting is disabled disengaging or disconnecting the VGA cable allows the laptop to be used but minus the 'eye-candy' that kwin has to offer. OBSERVED RESULT Laptop unusable not able to access anything normally. EXPECTED RESULT Laptop work smoothly as it would when docked or connected to the external monitor. SOFTWARE/OS VERSIONS OS : Linux Deepin kwin : kwin-5.15.8.61 ADDITIONAL INFORMATION I don't know if i can provide any debug data off of my system as i am not a techie(only a power user), but if someone gives me specific steps to run and grab the info that will aid you in identifying and fixing the issue, I would be most glad to provide such data. PS : Please find this issue highlighted at 2 other forums ... https://github.com/linuxdeepin/developer-center/issues/2140 https://unix.stackexchange.com/questions/681425/hp-laptop-docking-station-clean-connection-and-disconnection-on-debian-based-l -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448778] Unplugging an external monitor leads to a crash
https://bugs.kde.org/show_bug.cgi?id=448778 --- Comment #28 from aiamuzz --- @Zamundaaa ... firstly apologies for what may seem spamming your thread for additional help ... it only goes to show my desperation ... apologies for the same. Please find the commit from my distro team ... https://github.com/linuxdeepin/deepin-kwin/pull/82/commits/8530e2cbf5641b6e56cfb04a202ae95237f3dbc8 they have made this changes as per your commit ... https://invent.kde.org/plasma/kwin/-/commit/9f9ad7036518f0d0df984a3eda28e2b4c57607d3 I have a foolish(may be) question ... after your commit is patched by the affected user, will the monitor frequency show 60Hz or will it continue to show 60.01Hz ... ? ... reason i ask is my display properties is still showing 60.01Hz after patching my machine with the distro's patch ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448778] Unplugging an external monitor leads to a crash
https://bugs.kde.org/show_bug.cgi?id=448778 --- Comment #29 from aiamuzz --- @Zamundaaa ... any suggestions on the following ? https://github.com/linuxdeepin/developer-center/issues/3480#issuecomment-1323123155 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448778] Unplugging an external monitor leads to a crash
https://bugs.kde.org/show_bug.cgi?id=448778 aiamuzz changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410294] FEATURE REQUEST : Improving the 'Elegance Quotient' of kwin with additional controls at the discretion of the user to adapt them to their respective screen sizes !!!
https://bugs.kde.org/show_bug.cgi?id=410294 aiamuzz changed: What|Removed |Added Summary|Improving the 'Elegance |FEATURE REQUEST : Improving |Quotient' of kwin with |the 'Elegance Quotient' of |additional controls at the |kwin with additional |discretion of the user to |controls at the discretion |adapt them to their |of the user to adapt them |respective screen sizes !!! |to their respective screen ||sizes !!! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410294] New: Improving the 'Elegance Quotient' of kwin with additional controls at the discretion of the user to adapt them to their respective screen sizes !!!
https://bugs.kde.org/show_bug.cgi?id=410294 Bug ID: 410294 Summary: Improving the 'Elegance Quotient' of kwin with additional controls at the discretion of the user to adapt them to their respective screen sizes !!! Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: muzafsh@gmail.com Target Milestone: --- SUMMARY Hi All, I am a Linux Deepin User ... as you may already know Deepin has moved to kwinWM from its previous mutter based WM ... the older Deepin's mutter based WM was on hell of an elegant UI ... having moved to kwin i feel kwin is really big and has a lot of features ... but quite far from elegance. Elegance depends on proportions to relative items in the view ... I am writing this thread as a Feature Request to try and suggest some subtle changes to the existing setup/implementation in kwin so we can take these implementation closer towards elegance. Currently I use the 'Pager' as the layout mode ... the virtual desktops(workspaces) previews are aligned center verticall and horizontally and span across the width of the screen. Feature 1 : If we had an option to change the desktop preview frame sizes(as a whole pager strip ... not as an individual desktop thumbnail ) preferably on a percentage basis with regard to the width of the monitor ... it would give more control to the user which will be good for them and can play around with the right proportion wrt to their screen sizes. Feature 2 : further to the above size modification feature an option to play around with the distance between the individual desktop preview thumbnail will further help us improve the aesthetics of the layout. Feature 3 : Once the above option to increase/decrease the pager strip size and the option to change the spacing between individual desktop preview thumbnails is in place ... you could provide another option to postion this pager strip at the top / bottom ... and the option to position it on the / right / left of the screen can have a stacked arrangement instead of a strip Feature 4 : the rest of the real estate which gets freed up as a result of the above implementation can be used to display "Present windows" of the active desktop where we can move between them and activate them. The above arrangment will give a very simple and elegant look and UI for us to navigate bewteen the workspaces and the windows in each one of them ... This is exactly -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410294] FEATURE REQUEST : Improving the 'Elegance Quotient' of kwin with additional controls at the discretion of the user to adapt them to their respective screen sizes !!!
https://bugs.kde.org/show_bug.cgi?id=410294 --- Comment #1 from aiamuzz --- Feature 4 is not really a new feature but rather only an option to combine(enable) the "Present Window" Effect inside the "Desktop Grid" effect to be displayed in the freed up real estate as a consequence of modification from the requested Features 1-3 ... I will attach a snapshot shortly ... of whats the intended output with these features incorporated ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410294] FEATURE REQUEST : Improving the 'Elegance Quotient' of kwin with additional controls at the discretion of the user to adapt them to their respective screen sizes !!!
https://bugs.kde.org/show_bug.cgi?id=410294 --- Comment #2 from aiamuzz --- Created attachment 121781 --> https://bugs.kde.org/attachment.cgi?id=121781&action=edit A rendering of the desired final output/layout !!! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410296] New: FEATURE REQUEST : Present Windows Effect ... ability to change the size and spacing of the Window Preview thumbnails !!!
https://bugs.kde.org/show_bug.cgi?id=410296 Bug ID: 410296 Summary: FEATURE REQUEST : Present Windows Effect ... ability to change the size and spacing of the Window Preview thumbnails !!! Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: effects-present-windows Assignee: kwin-bugs-n...@kde.org Reporter: muzafsh@gmail.com Target Milestone: --- Created attachment 121782 --> https://bugs.kde.org/attachment.cgi?id=121782&action=edit A rendering of the desired final output/layout against the current implementation !!! Hi, This is my second feature request to further develop this effect so it can be modified to make it more elegant wrt the different user screen sizes ... Currently this effect specifically the Regular Grid Layout covers the whole screen end to end horizontally. I would request two options here ... 1. To be able to increase/decrease the size of this grid so that we can reduce it to the center of the screen at a more elegant proportion. 2. To be able to vary the distance between the window preview so that we can spread the windows in grid that best suits our screens aspect ratio's PS : I have attached a mockup of the current implementation (Top) ... versus the intended implementation (Bottom) ... i'e ... should this feature be executed -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410298] New: BUG : Incorrect window sizes previewed in the "Present Windows" Desktop effect !!!
https://bugs.kde.org/show_bug.cgi?id=410298 Bug ID: 410298 Summary: BUG : Incorrect window sizes previewed in the "Present Windows" Desktop effect !!! Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-present-windows Assignee: kwin-bugs-n...@kde.org Reporter: muzafsh@gmail.com Target Milestone: --- Created attachment 121784 --> https://bugs.kde.org/attachment.cgi?id=121784&action=edit A rendering of the Bug state and the corrected state after its fixed !!! Hi, Please find enclosed an attachment that describes the incorrect window sizes previewed in the Present Windows view ... As you can see on either side the real windows size with reference to the file manager window is seen for the Calculator & KDE System Settings Windows. The top Present Window Preview is displaying incorrect sizes of the Calculator & KDE System Settings Windows ... The are bigger than the full screen Movie Window and the Chrome Window ... Please find the Intended grid/layout at the bottom with the correct window sized ... should this bug be fixed/corrected !!! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410298] BUG : Incorrect window sizes previewed in the "Present Windows" Desktop effect !!!
https://bugs.kde.org/show_bug.cgi?id=410298 aiamuzz changed: What|Removed |Added CC|muzafsh@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410298] BUG : Incorrect window sizes previewed in the "Present Windows" Desktop effect !!!
https://bugs.kde.org/show_bug.cgi?id=410298 aiamuzz changed: What|Removed |Added CC||muzafsh@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410298] BUG : Incorrect window sizes previewed in the "Present Windows" Desktop effect !!!
https://bugs.kde.org/show_bug.cgi?id=410298 --- Comment #2 from aiamuzz --- Hello Martin, Great work with kwin ... saw that you are the driving force behind kwin By default mode you mean the 'Natural' Layout Mode ? yes i see that the window sizes are respected there ... but the way the windows are scattered(in the natural layout) ... is there a method to this scatter ? ... as i am a designer by profession my brain fails to see a method to this madness(we are wired to see elegance) ... even the spacing seems hap hazard ... in fact seems like its got some random grid behind it ... i can't reproduce the same scatter twice ... Would have been nice if there was a way to use true window sizes in a regular arrangment. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410294] FEATURE REQUEST : Improving the 'Elegance Quotient' of kwin with additional controls at the discretion of the user to adapt them to their respective screen sizes !!!
https://bugs.kde.org/show_bug.cgi?id=410294 --- Comment #4 from aiamuzz --- Created attachment 121791 --> https://bugs.kde.org/attachment.cgi?id=121791&action=edit A mutter based Deepin implementat ... this is the layout i was hoping to get on kwin with this request -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 410296] FEATURE REQUEST : Present Windows Effect ... ability to change the size and spacing of the Window Preview thumbnails !!!
https://bugs.kde.org/show_bug.cgi?id=410296 --- Comment #2 from aiamuzz --- oh ... hmm This look would have greatly improved if only the scaling option(request no. 1) was added ... By scaling i mean the whole windows grid could be scaled to the center so that sufficient padding around the grid could be achieved so as to match with the current spacing between the windows ... Is even this not possible ? If the option of scaling is too complex ... even a little padding added around the screen edges(top, bottom, right & left) would greatly improve the window layout. The current implementation where certain windows bleed on the edge of the screen puts this otherwise great layout out of aesthetics ... In simpler terms i am just hoping you set some margins around and then display the window layout/grid inside those margins ... imagine a word document without margins ... the text would really look ugly if it extended to the edge of the paper its printed on ... -- You are receiving this mail because: You are watching all bug changes.
