Version: (using KDE 4.1.0) Installed from: Unlisted Binary Package Compiler: gcc 4.3.1 OS: Linux Hi, The new plasma panel has no option to make it span across both Xinerama or Twinview screens. I request kicker's behaviour, which could do it.
I second this request, using 4.1.0 here on FreeBSD, and it would be great if the panel could "stretch" across the entire screen again.
*** Bug 172572 has been marked as a duplicate of this bug. ***
Yes please...me too.
I think this is a very important feature. Especially for those who have a laptop with an external monitor attached for dual-display. Say you have two widgets Digital Clock and System Tray on the external monitor's panel. If I were to undock the laptop I suddenly lose those widgets with no way to recover them (that I know of).
Michael Johnson, I think this reason does not justify the current behaviour at all. It is a very important feature for dualhead-users to fully utilize their screens (that does include the panel). Even for those laptop-users, it would be feasible to log out and in again (or restarting X, if you're the xinit-type) rather than just saying no to this request. If you're undocking the laptop, you are going to change places anyway, aren't you? But how about requesting to making it optional, so both sides are satisfied? It also might be more difficult to do than it appears to us humble users, as it seems that two screens seemingly are two different plasma containers (they have a cashew... uh... corner with plasma menu each). Greetings
Created attachment 31325 [details] Screenshot of a Dual Screen Monitor Please tell me that this doesn't look silly
Adding my support for this feature. I think I'll have to downgrade to KDE3.5 until this is resolved. If someone can point me in the right direction, I may have time to look at code...
*** Bug 169080 has been marked as a duplicate of this bug. ***
*** This bug has been confirmed by popular vote. ***
It is possible to add a second panel on the second monitor. In this way you can put two separate taskbar which displays windows of the own screen... imho it is much better than 3.5.
(In reply to comment #10) > It is possible to add a second panel on the second monitor. In this way you can > put two separate taskbar which displays windows of the own screen... imho it is > much better than 3.5. Problem is that currently, it is impossile to position or resize plasmoids on that second panel which makes it an un worakable solution. So I can't agree that its better than 3.x.
Oh.. If I remember correctly with 3.x you could have multiple panels and resize the panel and position applets as desired. Much more flexible.
you can resize the panel and position the applets on KDE 4 too... can you explain better what you mean? Thanks.
Panel Yes. Plasmoids No. And opening up a gazillion panels to get the same effect is resource intensive and silly.
Ah, I actually got used very well to this. Task manager and less important windows on the small laptop screen, serious work on the big screen in full, without a panel or anything else.
*** Bug 184879 has been marked as a duplicate of this bug. ***
*** Bug 200040 has been marked as a duplicate of this bug. ***
I used the 'place a second panel on the second monitor' work around for this bug. Since you cannot stack panels(bug https://bugs.kde.org/show_bug.cgi?id=165792), I added one on the top of one of my screens, but not the other. I use this as a quick launch bar. Now I cannot use the space on the top of the second monitor where the panel would be if I had one there. I simply *cannot* drag a window into that space. I can full screen an app and it will use that space though. So... the two biggest questions I have are, when will KDE 4.x finally have all the features from 3.5 that they dumped, and whose big idea was it to push out something that was not even close to ready? Seems we stole a play from Microsoft's Vista playbook...
*** Bug 247832 has been marked as a duplicate of this bug. ***
I'd add that separate containments for each screen has other daft consequences - for instance if I want desktop icons for my files (and I do) and the files take up more than one screen I'd like them to fill up screen 1 and then move onto screen 2. Under the current arrangement they fill up screen 1 then start again with the same files and fill up screen 2. If I arrange them alphabetically I get files A-N twice rather than A-N on screen 1 and O-Z on screen 2, how daft is that?
I'm also frustrated by this problem. I do appreciate the efforts - sure would be nice to see this polished.
I can confirm this is still a problem in kde 4.6.0 I found in kde4.6.0 that you can (in theory) turn off multiple monitor support (setup:display and monitor:multiple monitors). In my install (suse 11.4) the tickboxes seem broken (master tick for "enable multiple monitor support" doesn't activate the "apply" button - the others do so some pratting around is required). However non of these options make any difference to the actual behaviour. Turning everything off makes not a jot of difference (although I'd expect one big desktop), turning off specific features (like enable multiple monitor placement support) makes no difference, windows still snap to the boundary, maximise to the boundary etc etc. Ideally I'd like one desktop with the ability to let the desktop and taskbar span both monitors BUT I'd still like window placement, fullscreen and maximise to respect the boundary as it worked in kde 3.5. The taskbar placement is a constant annoyance and setup with icons on the desktop is completely broken.
Hello! This feature request was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this feature request is already implemented in Plasma 5, or is no longer applicable. Accordingly, we hope you understand why we must close this feature request. If the requested feature is still desired but not implemented in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham