Offset should still work with Alignment=1, Alignment=2

Bug #1115992 reported by CruelAngel
54
This bug affects 11 people
Affects Status Importance Assigned to Milestone
Plank
Triaged
Wishlist
Rico Tzschichholz

Bug Description

I wish to position my dock at the top left corner, but just a tiny bit lower, so it won't overlap with my top panel.
I understand that with Alignment=3 and Offset=-97(or whatever depending on screen and dock size) one could position the dock there, but opening/closing new apps, will move the dock up-down since the new apps change the dock size.

Now that alignments are implemented, I suggest that if a corner alignment (Alignment=1, Alignment=2) is set the offset would work as a margin from the selected corner. With that one could easily set the desired position accurately.

Thanks.

ps. I use the plank build from the elementary daily ppa.

Related branches

CruelAngel (hendricha)
description: updated
Robert Dyer (psybers)
summary: - Whislist: Offset should still work with Alignment=1, Alignment=2
+ Offset should still work with Alignment=1, Alignment=2
Changed in plank:
importance: Undecided → Wishlist
Changed in plank:
status: New → Triaged
Revision history for this message
Rico Tzschichholz (ricotz) wrote :

To achieve this and keeping the current preferences we need to change the interpretation of the Offset value. So Offset will specify the unrestricted amount of pixels shifting the dock's position. The shift direction will depend on the currently selected Alignment. The actual applied offset will be clamped to avoid off-screen positioning.

Changed in plank:
assignee: nobody → Rico Tzschichholz (ricotz)
Revision history for this message
Robert Dyer (psybers) wrote :

It doesn't need to be changed to pixels. You can still use percent. Percent of screen resolution *is* pixels, just compute the pixels based on the current Screen.

Revision history for this message
CruelAngel (hendricha) wrote :

As the original reporter of this bug I would be okay with Robert's proposision as well.

Revision history for this message
CruelAngel (hendricha) wrote :

*proposition

Revision history for this message
Rico Tzschichholz (ricotz) wrote :

@Robert: Right, my thinking here is to be able to specify the shift in a reasonable accuracy. (e.g. 1% == 19px on a 1920x1080 screen which is why I think using a pixel value would be easier) Otherwise Offset should be a double which isn't that nice though.

Revision history for this message
Robert Dyer (psybers) wrote :

But with Offset as a percentage, as it is now, you don't have to worry about where the dock appears when a resolution change happens. It is always in the same vicinity. This behavior is similar to how Alignment works. Right-aligned docks *always* are right aligned, even if I change my resolution. Keeping it as a percentage makes them both behave in the same way, so you can easily just have your dock 'on the left 1/3' etc. Frankly, the Alignment is redundant, as you can specify 0% Offset, -100% Offset, and +100% Offset to get the same effect.

I am highly inclined to remove the Alignment.

Revision history for this message
Robert Dyer (psybers) wrote :

To me, the fact that Alignment can physically move the dock left/right just seems wrong. Offset should anchor the dock into 1 location, and Alignment simply change how it grows from that point.

Of course we can still keep Align=0 as a 'panel' like full-width. But =1 and =2 need to change.

Revision history for this message
Felipe Castillo (fcastillo.ec) wrote :

Has any update been made in this area? The last post was over 3 years ago and I still don't see a way to set my Plank aligned start with an offset.
Any workarounds?

Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote :

Same story here, left edge, need space for top panel (which has controls on the left end)

Revision history for this message
Sancho (sashb) wrote :

+1

Revision history for this message
Sancho (sashb) wrote :

There is even a patch on the right side. I don't understand why the patch is not yet included.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.