You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem here is that the automatic title placement is interfering. However, I admit I'm a little flummoxed why it is only a problem for the last title.
I think there is a reasonable argument that if the user specifies padory they mean for the title to be placed manually.
So this is a bit of a funny one. If you remove sharex=True, none of them are placed with the pad, which is expected behaviour, if a bit undesirable. Basically, the idea of the automatic placement of titles is that you don't want it to overlap axes. So it adjusts upwards, even if pad=-40 until it no longer overlaps.
However, if you set sharex=True the axes without xticks and xlabel have the axes position determined by ax.get_window_extent which at this point in the draw cycle is "None". That leads to the first two axes looking like they are obeying the pad.
Activity
jklymak commentedon Oct 20, 2021
As a workaround you can do
The problem here is that the automatic title placement is interfering. However, I admit I'm a little flummoxed why it is only a problem for the last title.
I think there is a reasonable argument that if the user specifies
padorythey mean for the title to be placed manually.jklymak commentedon Oct 20, 2021
So this is a bit of a funny one. If you remove
sharex=True, none of them are placed with the pad, which is expected behaviour, if a bit undesirable. Basically, the idea of the automatic placement of titles is that you don't want it to overlap axes. So it adjusts upwards, even if pad=-40 until it no longer overlaps.However, if you set
sharex=Truethe axes without xticks and xlabel have the axes position determined byax.get_window_extentwhich at this point in the draw cycle is "None". That leads to the first two axes looking like they are obeying the pad.