Fix top and bottom clipping in raw.plot()

[cbrnr]

Previously, annotation labels positioned above the plot, as well as the x-axis label below it, were clipped and therefore unreadable using the matplotlib backend.

This PR addresses the issue by repositioning annotation labels within the plot area and increasing the bottom spacing to ensure the x-axis label is fully visible.

Before:

After:

Note that I've observed these issues on Linux, so I think it would be good to verify that the changes still render correctly also on macOS and Windows.

from numpy.random import default_rng

import mne
from mne import create_info
from mne.io import RawArray

mne.viz.set_browser_backend("matplotlib")


def create_toy_data(n_channels=3, duration=25, sfreq=250, seed=None):
    rng = default_rng(seed)
    data = rng.standard_normal(size=(n_channels, duration * sfreq)) * 5e-6
    info = create_info(n_channels, sfreq, "eeg")
    return RawArray(data, info)


raw = create_toy_data()
raw.set_annotations(
    mne.Annotations(onset=[1, 5], duration=[1, 2], description=["test", "bad"])
)
raw.plot(block=True)

[cbrnr]

Still looks good on macOS, even though the fix was not needed there.

Before:

After:

[cbrnr]

Looks good on Windows too.

Before:

After:

[cbrnr]

If events are also present, the plot still looks fine (I've increased the annotations z-order such that the vertical event line is behind):

[wmvanvliet]

I'm on linux too and don't seem to get your bug:

The like the yourchanges to the margins though, looks a bit better to me.

[cbrnr]

Could be related to Wayland vs. X11. What do you use? But as you said, I also think that it looks better with the new layout.

[wmvanvliet]

Tested on both XWayland (QT_QPA_PLATFORM=xcb) and Wayland proper (QT_QPA_PLATFORM=wayland-egl). Both look fine.

[cbrnr]

I can reproduce the issue on two different machines. Whatever the difference is, you agree that the new layout is better, right?

[wmvanvliet]

I wonder what causes the difference on your machine (just tested on another linux machine... works fine). But yes, I'm not against this change, because on my machines the new version also works great and it if fixes things for your machine then perhaps there are other machines out there with the same issue.

[wmvanvliet]

sorry about the previous comment. That was not meant for this thread at all, nothing is broken for me 😄

[cbrnr]

@drammock and/or @larsoner this is ready for review.