Bug 373860 - Plasmoids cannot be placed at the screen edge
Summary: Plasmoids cannot be placed at the screen edge
Status: RESOLVED DUPLICATE of bug 358418
Alias: None
Product: plasmashell
Classification: Plasma
Component: Desktop Containment (show other bugs)
Version: 5.8.2
Platform: Debian testing Linux
: NOR normal
Target Milestone: 1.0
Assignee: Sebastian Kügler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-18 19:50 UTC by Alex
Modified: 2020-01-22 18:53 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Plasmoid near the screen edge behind a semi transparent terminal. The plasmoid cannot be moved at the lower edge. (8.24 KB, image/png)
2017-01-02 07:58 UTC, Alex
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alex 2016-12-18 19:50:20 UTC
When placing a plasmoid on the desktop at a screen edge (i.e. bottom of plasmoid to the bottom of the screen), it slides up a bit. When i move the plasmoid on the screen back to to bottom, it slides up again. With plasma4, it worked to place it directly on the edge.
Comment 1 Christoph Feck 2016-12-21 03:23:20 UTC

*** This bug has been marked as a duplicate of bug 358990 ***
Comment 2 Christoph Feck 2016-12-21 19:07:22 UTC
Not a duplicate, sorry.
Comment 3 Alex 2016-12-21 19:13:13 UTC
Copy&Paste of der extended description (how this differes from the other bug):

This is [...] about free positioning of plamoids, i.e. the timer plasmoid, which is placed in some corner behind a semi-transparent terminal on my desktop.

In KDE 4 it was easy to start the timer, as there are ~15 Pixel between screen bottom and terminal bottom. In Plasma 5, the timer placed on the screen bottom slides up like 10 pixels, leaving only about 5 pixels to click for starting the timer.
Comment 4 Eike Hein 2017-01-02 06:29:30 UTC
Can you add a screenshot of your problem?
Comment 5 Alex 2017-01-02 07:58:32 UTC
Created attachment 103138 [details]
Plasmoid near the screen edge behind a semi transparent terminal. The plasmoid cannot be moved at the lower edge.
Comment 6 Alex 2017-01-02 08:03:16 UTC
Added a screenshot.
In my Plasma 4 setup, the plasmoid was at the very bottom of the screen, leaving a bit of room.

The semi transparent terminal has more or less fixed size, as it can only be resized by full terminal-lines.
In plasma 4 I used this space between the terminal and the screen edge, which cannot be removed anyway, so I can click the plasmoid.
Comment 7 Eike Hein 2017-01-02 08:29:04 UTC
I'm not sure I understand based on the screenshot ... the margin between the screen edge and the plasmoid seems fine to me.
Comment 8 Alex 2017-01-02 15:52:25 UTC
I had the same configuration with plasma 4, but the plasmoid had 0px distance to the screen edge. When i now drag it to have 0px distance, it slides back to the distance it has in the screenshot. Like it would have a invisible border in plasma 5 or something similiar, which prevents it from being placed too near to the edge.
Comment 9 Eike Hein 2017-01-03 06:20:10 UTC
I think what's going on is that Plasma 4 allowed you to place widgets freely on every pixel, but we had countless user requests that this made it hard to line widgets up nicely, so we implemented a grid system. After dragging widgets may slide slightly to align to the nearest cell.
Comment 10 Alex 2017-01-03 07:29:43 UTC
Ah, that's quite possible, that the grid does not end on the exact screen edge and the widget aligns with the bottom line of the grid instead of the bottom of the screen.
Comment 11 Eike Hein 2017-01-03 07:35:51 UTC
This might be it, but it could also be two other reasons:

(a) Invisible margin in the Plasma theme outside the visible edge of the widget frame
(b) For some reason (e.g.: intentionally for aesthetic reasons) widgets aren't allowed to be placed in the last cell

Needs actually looking at the code.

Now, personally I will say that I think some extra margin is nice aesthetically ...
Comment 12 Alex 2017-01-03 07:41:14 UTC
Yes, then it seems like intentional behaviour, which just changed.
Comment 13 Nate Graham 2020-01-22 18:53:34 UTC
(In reply to Alexander Schier from comment #12)
> Yes, then it seems like intentional behaviour, which just changed.
Yeah.

*** This bug has been marked as a duplicate of bug 358418 ***