<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/foot.git/wayland.c, branch 1.5.2</title>
<subtitle>A fast, lightweight and minimalistic Wayland terminal emulator</subtitle>
<id>https://git.0x0f.dev/mirrors/foot.git/atom?h=1.5.2</id>
<link rel='self' href='https://git.0x0f.dev/mirrors/foot.git/atom?h=1.5.2'/>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/'/>
<updated>2020-09-04T15:56:40Z</updated>
<entry>
<title>wayland: register xdg-output interface on pre-existing output objects</title>
<updated>2020-09-04T15:56:40Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-09-04T15:56:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=f2c59f8608218ea3270ee106d93af0cbcf9d831c'/>
<id>urn:sha1:f2c59f8608218ea3270ee106d93af0cbcf9d831c</id>
<content type='text'>
The XDG output manager object may arrive *after* output objects. In
this case, we need to register the pre-existing output objects with
the XDG output manager.

This fixes an issue with some monitors having a DPI value of 0 on
Gnome/mutter, which resulted in incorrect font sizes.
</content>
</entry>
<entry>
<title>render: render-timer: position sub-surface similar to the scrollback indicator</title>
<updated>2020-08-14T05:48:40Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-08-14T05:48:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=640445acb48bceef6c1734248902bdb685d64869'/>
<id>urn:sha1:640445acb48bceef6c1734248902bdb685d64869</id>
<content type='text'>
</content>
</entry>
<entry>
<title>wayland: global-remove: return after finding a matching seat</title>
<updated>2020-08-13T16:47:19Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-08-10T16:58:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=49eea3893e91b6c3df90e53c0403a976bf1cda52'/>
<id>urn:sha1:49eea3893e91b6c3df90e53c0403a976bf1cda52</id>
<content type='text'>
</content>
</entry>
<entry>
<title>wayland: global-remove: fix call to pointer_listener.leave()</title>
<updated>2020-08-13T16:47:19Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-08-10T16:57:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=6b18bd998a08eee404fbdb73a1a71627377b874b'/>
<id>urn:sha1:6b18bd998a08eee404fbdb73a1a71627377b874b</id>
<content type='text'>
Don't call it when we have keyboard focus, call it when we have mouse
focus.
</content>
</entry>
<entry>
<title>config: wip: add support for modifiers in mouse bindings</title>
<updated>2020-08-13T16:47:19Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-08-09T20:40:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=544c1b1976544085a2f27497c5c516bf1d9edfa3'/>
<id>urn:sha1:544c1b1976544085a2f27497c5c516bf1d9edfa3</id>
<content type='text'>
Mouse bindings can now include modifiers. They are specified in pretty
much the same way as in keyboard bindings:

  Control+BTN_LEFT
</content>
</entry>
<entry>
<title>config: add tweak.render-timer option</title>
<updated>2020-08-13T16:35:17Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-08-13T16:35:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=17070a0d54e66641839805c68cfe1670c7012525'/>
<id>urn:sha1:17070a0d54e66641839805c68cfe1670c7012525</id>
<content type='text'>
This can be set to 'none' (the default), 'osd', 'log' or 'both'.

When 'osd' is enabled, we'll render the frame rendering time to a
sub-surface after each frame.

When 'log' is enabled, the frame rendering time is logged on stderr.
</content>
</entry>
<entry>
<title>Handle allocation failures explicitly in *_init() functions</title>
<updated>2020-08-09T07:55:20Z</updated>
<author>
<name>Craig Barnes</name>
<email>craigbarnes@protonmail.com</email>
</author>
<published>2020-08-09T07:55:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=4e6100494c4fdea43cb95df1abb68958a89d7935'/>
<id>urn:sha1:4e6100494c4fdea43cb95df1abb68958a89d7935</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Convert most dynamic allocations to use functions from xmalloc.h</title>
<updated>2020-08-08T19:37:57Z</updated>
<author>
<name>Craig Barnes</name>
<email>craigbarnes@protonmail.com</email>
</author>
<published>2020-08-08T19:34:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=7a77958ba20c2b344be5e66e69e2f212a4bbf6b3'/>
<id>urn:sha1:7a77958ba20c2b344be5e66e69e2f212a4bbf6b3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'master' into diagonal-dpi</title>
<updated>2020-07-28T18:01:56Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-07-28T18:01:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=295083059ca8f642437abf44329698d1bbbb0067'/>
<id>urn:sha1:295083059ca8f642437abf44329698d1bbbb0067</id>
<content type='text'>
</content>
</entry>
<entry>
<title>wayland: add scrollback indicator surface + sub-surface to wl_window</title>
<updated>2020-07-26T08:00:50Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-07-26T08:00:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=2815c1c0764cbc79625aa9c6623601d2188e0500'/>
<id>urn:sha1:2815c1c0764cbc79625aa9c6623601d2188e0500</id>
<content type='text'>
</content>
</entry>
<entry>
<title>wayland: calculate a single, scaled DPI value</title>
<updated>2020-07-26T05:41:57Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-07-26T05:41:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=e955a14dd0bf7ed23a9e42f28a93e3357643300c'/>
<id>urn:sha1:e955a14dd0bf7ed23a9e42f28a93e3357643300c</id>
<content type='text'>
Previously, we calculated the monitors horizontal and vertical PPI
values.

For font sizing, we used the vertical PPI value. It seems however,
that using the diagonal PPI value, i.e. diagonal_px / diagonal_inch,
gives more consistent results.

This is still a PPI value, but since it is intended to be used as a
FontConfig DPI value, name it 'dpi'.
</content>
</entry>
<entry>
<title>wayland: don't assume data-device globals are added before seats</title>
<updated>2020-07-16T15:47:47Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-07-16T15:47:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=067cf6ccb176abc5a73715214e5d602c99c74106'/>
<id>urn:sha1:067cf6ccb176abc5a73715214e5d602c99c74106</id>
<content type='text'>
When we're handling the initial set of globals, the data-device and
primary-selection-device objects may, or may not be registered before
the seat(s).

We need to handle both cases.

When adding a seat, instantiate the data-device and
primary-selection-device **if available**.

When adding the device objects, instantiate them on **all** currently
available seats.
</content>
</entry>
<entry>
<title>wayland: configure: do a regular resize instead of a force resize</title>
<updated>2020-07-13T13:01:27Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-07-13T13:01:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=d169e9634603a2ec84bb18c975cdb06f5e3551dc'/>
<id>urn:sha1:d169e9634603a2ec84bb18c975cdb06f5e3551dc</id>
<content type='text'>
The commit log says that was needed to get tiling in GNOME
working. However, I don't know *which* extension that was.

Force resizing in a configure event means we'll trash a perfectly
valid buffer on e.g. 'activated' state changes.

So, let's revert this for now, and if this breaks GNOME, let's try to
find another solution. If worse comes to worse, we can detect if we're
running under GNOME and do a force-resize then, but not on sane
compositors.
</content>
</entry>
<entry>
<title>wayland: destroy cursor theme when removing pointer capability</title>
<updated>2020-07-10T17:32:48Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-07-10T17:32:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=1c13061f35b2d826bee931dee2a00d911173a946'/>
<id>urn:sha1:1c13061f35b2d826bee931dee2a00d911173a946</id>
<content type='text'>
</content>
</entry>
<entry>
<title>wayland: seat: instantiate pointer surface in capabilities event</title>
<updated>2020-07-10T17:24:33Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-07-10T17:24:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=5677df629e4323c8e8ca24d11dd63725934a4c98'/>
<id>urn:sha1:5677df629e4323c8e8ca24d11dd63725934a4c98</id>
<content type='text'>
This way we only instantiate the surface for seats that actually have
a pointer.
</content>
</entry>
<entry>
<title>wayland: read XCURSOR_{THEME,SIZE} in reload_xcursor theme</title>
<updated>2020-07-10T10:06:55Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-07-10T10:06:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=bf62519d8330204b12e9e3743fb332e3abde0ed0'/>
<id>urn:sha1:bf62519d8330204b12e9e3743fb332e3abde0ed0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>wayland: globals: destroy: seat: use keyboard/pointer listener interfaces</title>
<updated>2020-07-09T06:52:39Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-07-09T06:52:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=a6da07b3dd8771ecf9bb2cfb3149506525e1ef53'/>
<id>urn:sha1:a6da07b3dd8771ecf9bb2cfb3149506525e1ef53</id>
<content type='text'>
</content>
</entry>
<entry>
<title>wayland: globals: destroy: handle seats being destroyed</title>
<updated>2020-07-09T06:47:56Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-07-09T06:47:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=b6342bb36d83054968a1d413ccf983f6ffc0366c'/>
<id>urn:sha1:b6342bb36d83054968a1d413ccf983f6ffc0366c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>wayland: log: be clear that these are the XCRUSOR_* environment variables</title>
<updated>2020-07-08T18:04:02Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-07-08T18:04:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=98f3ccfe79b37122f879174e315df407e7f4e09d'/>
<id>urn:sha1:98f3ccfe79b37122f879174e315df407e7f4e09d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>xcursor: trigger theme reload in pointer-enter event</title>
<updated>2020-07-08T17:52:17Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-07-08T17:52:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=d377221e247f67f7b5e6363f81ae2268e16aa32d'/>
<id>urn:sha1:d377221e247f67f7b5e6363f81ae2268e16aa32d</id>
<content type='text'>
Previously, we triggered a theme reload on output changes. This is
completely wrong. We may get a new output with a scale different from
the output the pointer is actually on.

Now, we store the current scale along with the theme. We then trigger
a call to reload the xcursor theme *every* time the pointer enters a
surface. When it does, we use the current scale factor of the terminal
that owns that surface.

If the terminal covers multiple outputs, with different scale factors,
we'll use the largest scale factor. This may not be 100% correct. But
to fix that, we'd need to track which regions of a surface are mapped
on which outputs. Too complicated I say.
</content>
</entry>
</feed>
