…1676)

When zoom changes on a manual layout icon view, the available area
changes and can lead to some icons to either overflow or be able to go
back to their actually saved position.

This is done correctly when the view is reloaded entirely, but not
in response to zoom change, leading to disappearing icons (when zoom
increases) or unexpected empty space (when zoom decreases).

Fix this by re-computing actual positions based on saved positions when
zoom changes, to match what would actually happen when the view gets
loaded.

This PR enables the displaying of Caja (as a file manager) for use in Budgie Desktop and XFCE. Prior to this commit, it would only be able accessible in MATE or with downstreams like Fedora patching in the support. The addition of these is important as file managers such as Nautilus adopt libadwaita and begin to directly come into conflict with user theming choices.

`name_row` is not needed since GTK2 support was dropped with commit
276eb14.

Found by cppcheck: https://caja.mate-desktop.dev/2022-11-23-174623-5790-cppcheck@ae663c369cf2_desktop-no-overflow/73.html#line-101

Based on a cppcheck report: https://caja.mate-desktop.dev/2022-11-23-174623-5790-cppcheck@ae663c369cf2_desktop-no-overflow/

Found by cppcheck: https://caja.mate-desktop.dev/2022-11-23-174623-5790-cppcheck@ae663c369cf2_desktop-no-overflow/18.html#line-630

This is actually an opaque type, and there is no definition of struct
CajaIconData anywhere.  This actually doesn't change anything as the
non-existent struct is equivalent to any other incomplete type, and
works fine so long as the pointers are not dereferenced using that
incomplete type.

However, change this to an explicit `void` to make it clear it's an
opaque pointer and stop people from looking for a struct CajaIconData
that is nowhere to be found.

Properly update the icon data before placing the icon, because
positioning might depend on full icon contents on the desktop, whereas
updating contents don't care about position.

When an icon position overflows the desktop area, it is clamped to stay
in the visible area, but this computation depends on accurate icon and
label sizes, which is only available when the icon is fully loaded.

Fix the code to first load the contents and then position instead of
the other way around, which was actually trivial.

Note that visible positions were most often correct anyway for two
reasons:

1. Most of the time icons do not overflow, as they are positioned on
   the final desktop size anyway.  It however can easily happen
   reducing monitor resolution or increasing desktop view zoom.
2. A second layout pass happens most of the time (I'm not yet sure why
   and when though), but not when an update is triggered before the
   previous one terminated (e.g. quickly hitting F5 twice).

`p` actually could never be `0` (because of the NULL check on the
`memchr()` call), but the intended behavior is `*p == '\0'`: the
containing condition checks for either a truncated data (`*p == '\0'`)
or no geometry information (`*p == '\n'`).

I replaced the check to be `*p != '\n'` instead of `*p == '\0'` to
make this more robust as the actual issue is anything but a newline,
the fact it can only be a NUL otherwise is incidental to the enclosing
check, but not really relevant at this level.  This is also in line
with the actual error message.

Found by cppcheck: https://caja.mate-desktop.dev/2022-11-23-174623-5790-cppcheck@ae663c369cf2_desktop-no-overflow/16.html#line-204

based on https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/821/diffs

If informal date format is used, the yesterday/today ranges of 48/24
hours apply to the end of the current day, not to the current instant.

Fixes a regression introduced by 476f56a.
Fixes #1621.

If informal date format is used, for future dates the today time format
has been used by mistake, instead of the general time format.

    search popup

    This gets mis-handled in wayland as a standalone window and
    is treated as such (like getting tiled next to the main caja window).
    Ported over from Nemo

fix #1069

*In x11 we can anchor the desktop size to the root window
instead of the screen or (possibly multiple)monitors

*revert x11 icon position handling to the older and well tested code
*use the newer code only in wayland where all the screen can already be used

* Wayland: Support rendering the desktop

*Wayland support is optional via the --enable-wayland option

* eel-editable-label-c: remove unused variable

This was leftover from earlier code compatable only with x11

* Fix gtk-layer-shell-0 version check, improve error message when Wayland requested but not found