| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
backend/drm: update output enabled property on modeset
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Screenshot transform
|
|
The inverse loop iterations for the transformed outputs had an off by
one error, iterating 1 based, not 0 based. This commit fixes that.
|
|
output: add destroy signal for wlr_output_cursor
|
|
|
|
This handles all current transformations for outputs properly.
This ensures an output is drawn in readable orientation/flipping no
matter the actual transformations applied to it.
|
|
This fixes the screenshot example application when an output is rotated
by 90 degrees.
Other tranformations are not taken into account yet.
|
|
|
|
|
|
The backend destroy signal is emitted before the output_remove
signal is. When the destroy signal is emitted listeners remove
their output_remove listener, so the output_remove signal is never
received and listeners have an invalid output pointer.
The correct way to solve this would be to remove the output_remove
signal completely and use the wlr_output.events.destroy signal
instead. This isn't yet possible because wl_signal_emit is unsafe
and listeners cannot be removed in listeners.
|
|
Fix some typos
|
|
Prefer initialize over initialise since used more often in the sources.
|
|
|
|
|
|
util/region: add wlr_region_expand
|
|
relases gbm buffers on init
|
|
output: add wlr_output_transformed_resolution
|
|
|
|
|
|
|
|
Backport screenshooter fixes from the renderer redesign v1
|
|
|
|
The wlr_drm_surface_init function is called (upon others) when the drm
mode is changed.
When the surface was used previously this replaced the gbm_surface, but
did not replace the gbm buffers (front/back).
With this, wlr_drm_surface_get_from never set up the new buffers with
the new glViewport because surf->front existed.
This frees the buffers to get new buffers on the new surface with the
new viewport.
|
|
|
|
|
|
This should solve issues with multiple outputs on DRM backend.
|
|
This should fix artifacts when leaving fullscreen on rotated outputs.
|
|
Fix assertion failed in data_source_notify_finish
|
|
|
|
|
|
|
|
|
|
Fix building rootston without XWayland
|
|
Right now, we are adding systemd and elogind backends to the build
system as soon as their libraries are found on the build system.
Instead, we should only add them if the libraries have been found _and_
the user has actually requested them to be included.
|
|
Recently, the support for building rootston without XWayland was broken.
While the breakage was easily fixable, the more important problem is
that actually nobody seems to ever compile wlroots without XWayland,
causing silent breakage. This problem can easily be handled by the CI
system: in addition to the existing job which enables XWayland, add a
second job which compiles wlroots without XWayland. This will catch
breakage at a much earlier stage.
Catching broken builds without XWayland support obviously only covers
one part of a greater issue, as all the other options may cause our
builds to break, too. While we cannot test each combination, we can at
least make sure to have one build with all options enabled and one with
all options disabled.
|
|
The XWayland code for creating the cursor as well as creating the
surface itself are currently split up into two ifdef'ed sections in
`desktop_create()`. Move together these two sections in order to avoid
having multiple ifdefs as well as making it clearer that they do in fact
serve the same purpose of setting up the XWayland environment.
|
|
In case wlroots is not being compiled with XWayland support, we will not
have an xwayland surface in our roots view. While we make sure to pay
attention to that in some places, we are not being consistent and try to
access the xwayland surface in other places. Obviously, this leads to a
compiler error due to the field not being present.
Fix the issue by sprinkling in a few additional ifdefs where required.
|
|
|
|
|
|
|
|
|
|
Fix warnings on arm-linux
|
