[1.18] mate sensors applet dont respect its position. #41

Closed
javashin opened this Issue Mar 15, 2017 · 8 comments

Comments

Projects
None yet
5 participants

javashin commented Mar 15, 2017

hello the mate-sensors-applet-1.18.0 is not showing in the correct place in the mate panel i installed just with configure --prefix=/usr and i had to downgrade to the 1.16.0 version in order to make it work like it has to be here is a screenshot in the correct place with old verision inside full mate 1.18
screenshot at 2017-03-14 20-59-22

and here is the mate-sensors-applet 1.18.0 in a way other level with the same configuration as the other screenshot
screenshot at 2017-03-14 21-03-32

this is gentoo with mate 1.18 gtk3 all compiled with:
CFLAGS="-march=westmere -mtune=westmere -O2 -pipe -fstack-protector-strong"
everything is working like it has to be only mate-sensors applet have this issue so far . thanks in advance.

Owner

flexiondotorg commented Mar 15, 2017

EDIT: OK, I see it now. In the second screenshot the CPU sensors are offset vertically.

cool

Member

monsta commented Mar 17, 2017

Confirmed. Looks like a regression from 0392b7a. 😞

@monsta monsta added the confirmed label Mar 17, 2017

@monsta monsta changed the title from mate sensors applet dont respect its position. to [1.18] mate sensors applet dont respect its position. Mar 17, 2017

Member

raveit65 commented Mar 18, 2017

We need to set valign=GTK_ALIGN_CENTER to the whole GtkGrid, than every sensor is in the middle of the panel. The default GTK_ALIGN_FILL isn't useful here.
You can test this in runtime with gtk3-inspector and set up this in inspectors properties page for the grid.
I guess for a vertical panel we need halign=GTK_ALIGN_CENTER.

raveit65 added a commit that referenced this issue Mar 18, 2017

Member

lukefromdc commented Mar 18, 2017

confirmed

@monsta monsta closed this in #42 Mar 19, 2017

Member

monsta commented Mar 19, 2017

@javashin: fixed in 6dd3a48, you can make a patch from that commit (we will release 1.18.1 later).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment