Commit graph

6670 commits

Author SHA1 Message Date
alexei-zebra
4d1b4a1638
Redraw the windows frame from WM_SIZE and keep its style
The refresh callback is triggered by WM_PAINT, but windows does not send it
while a border is dragged: the window class has neither CS_HREDRAW nor
CS_VREDRAW and nothing invalidates the client area. Only WM_SIZE arrives, so
nothing was drawn during such a resize. The frame is drawn from WM_SIZE now,
after forwarding the message to GLFW so that the new size is already in.

WM_NCHITTEST re-applies the style bits the engine frame needs and which GLFW
drops on every window mode change, taking the drag area with them. Every frame
setup logs whether the subclass had to be installed again, so a lost window
procedure is visible in the log.

The live resize switch is honoured by the GLFW backend as well: with it off the
frame from the message loop is skipped and the window keeps showing what the
system stretches.
2026-10-11 01:05:47 +03:00
alexei-zebra
4f9b125e17
Record where the wayland protocol descriptions come from
They are vendored on purpose: they come from wayland-protocols rather than
libwayland, they are newer than the 1.25 of older distributions, and the build
has to work offline and from a source archive.
2026-10-10 23:04:27 +03:00
alexei-zebra
74a28cebe5
Fix the windows frame hang and center new windows
The frame is set up again after every window mode change, but it subclassed
the window procedure each time and stored our own procedure as the original
one. Every message we do not handle then went through CallWindowProc straight
back into ourselves: the window hung, and repaint messages were lost with it,
which is what broke the live rendering during a resize.

The subclass is installed once now, while the window style is still re-applied
on every mode change.

New windows are also placed at the center of the monitor work area instead of
the top left corner. This only happens where the platform lets the client place
its window, which wayland does not.
2026-10-10 23:04:27 +03:00
alexei-zebra
68d4214627
Fix the engine window frame on windows
Four things came out of testing on windows.

The window settings were hidden outside of wayland because the check used
the backend name, while the bar height matters wherever the engine draws
the frame. The window now reports that (hasEngineFrame: barEnabled on
wayland, engineFrame on glfw) and the display page asks for it. Only the
live resize switch stays wayland specific, since the glfw backend always
draws a fresh frame.

The simplified mode is gone: when the frame is active and the surface has
alpha, the shadow and the outer resize border are always there.

The bar and its controls are drawn even when the font is missing: the early
return used to make the whole bar invisible while its hit zones kept
working.

GLFW rewrites the window style on every mode change and dropped the thick
frame the native resize border and snapping need, so the frame is set up
again after such a change.

Windows runs a modal loop while a window border is dragged and the main
loop is blocked inside it, which froze the content during a resize. The
backend draws and presents a frame from the refresh callback now, and
skips the framerate limit there.
2026-10-10 22:02:33 +03:00
alexei-zebra
4bc81af726
Include glfw3.h before glfw3native.h
glfw3native.h needs the GLFWmonitor, GLFWwindow and GLFWAPI declarations of
glfw3.h, so the windows build failed on the win32 branch. Only that branch
is affected: x11 resolves the GLFW accessors with dlsym and does not include
the native header at all.
2026-10-10 16:10:04 +03:00
alexei-zebra
f13b75475f
Let the window frame keep its cursor
The GUI sets the cursor of the hovered widget every frame, and over the
window that widget is usually the background with a plain arrow. The frame
sets its resize cursors on pointer motion, so the GUI replaced them on the
next frame: hovering a window edge did not show a resize cursor, it flickered
and stayed an arrow.

The window now reports whether the frame owns the cursor, and the GUI only
sets the hovered cursor when it does not. The GLFW backend claims it inside
the frame and gives it back in the client area together with the arrow, since
the GUI sets a cursor only while a widget is hovered.

Wayland keeps returning false, so the GUI behaves exactly as before there.
2026-10-10 16:04:39 +03:00
alexei-zebra
7126158d68
Keep the window frame usable without a window manager
frame_has_native_operations() trusted the X11 accessors of GLFW alone, but a
window manager that does not advertise _NET_WM_MOVERESIZE drops the request
silently: on a plain X11 session the frame asked it to move and resize the
window and nothing happened at all. The root window is checked for the atom
now, and the frame falls back to moving and resizing the window itself.

The resize edges also win over the bar instead of the bar swallowing its top
strip, which made the top edge and the top corners impossible to grab.

Both backends log the active path as
"engine window frame: on, window manager operations are on|off".
2026-10-10 15:51:32 +03:00
alexei-zebra
56a225fe15
Draw the window frame on windows and on x11
The engine already draws the bar on wayland; the GLFW backend now does the
same where the client may move its own window, and keeps the native frame
elsewhere: wayland forbids client side positioning, and macOS has its own
frame.

On windows the native frame is kept and only its caption is hidden, so the
thick frame, the shadow, the animations and the snap layouts keep working.
A window procedure returns HTCAPTION for the bar, HTCLIENT for the controls
and HT* for the edges. On x11 the window manager runs the interactive move
or resize (_NET_WM_MOVERESIZE), which keeps window snapping and tiling
native too. Where neither is available the frame moves and resizes the
window itself, as before.

The X11 accessors of GLFW are resolved with dlsym, so a wayland-only build
still links, and the window manager operations are only compiled in when
X11 is found.

The title of the window is stored on creation now: the bar draws it, and
the GLFW backend used to leave it empty.
2026-10-10 15:30:55 +03:00
alexei-zebra
b9a13c853d
Give the window backends the engine include surface
VoxelWindowBase only got the src include directory, so BaseInput.cpp could
not find glm/vec2.hpp through window/input.hpp on macOS, where glm lives in
a prefix outside the default include path. VoxelGLFW had glm linked, which
hid the problem on Linux, where glm sits in /usr/include anyway.

The backends now link a single interface target carrying the engine sources
and the third-party headers their public headers pull in, instead of each
backend keeping its own list.
2026-10-10 14:20:33 +03:00
alexei-zebra
aac0bfa44a
Build the window backends as separate libraries
VoxelGLFW, VoxelWindowBase (the input state both backends share) and
VoxelWayland own their sources, dependencies and protocol generation,
while VoxelCoreSrc only sees the Window/Input interfaces and the
factories declared in detail/WindowBackends.hpp.

VOXELCORE_WAYLAND now only selects the subdirectory to add and the
library to link, and the wayland library defines the macro for whoever
links it, so linking the backend is what enables it. The protocol sources
are generated inside build/src/window/wayland, and missing dependencies
only turn the backend off instead of breaking the configuration.
2026-10-10 14:15:40 +03:00
alexei-zebra
b558beeea3
Fix the build with the wayland 1.20 headers
axis_value120 (wl_pointer version 8) and axis_relative_direction (version
9) do not exist in the headers older distributions ship, which broke the
build on ubuntu 22.04.

They are not needed anyway: a pointer inherits the version of its seat,
which is bound at version 7 here, so the compositor cannot send those
events at all. The version cap now documents that the listener covers it
and that raising it requires handling the newer events too.
2026-10-10 14:15:40 +03:00
alexei-zebra
714567a06e
fix names 2026-10-10 12:34:52 +03:00
alexei-zebra
aac67ac93a
fix README.md 2026-10-10 12:23:42 +03:00
alexei-zebra
27a58b584e
Fix black frames of the simple window and rename its setting
Without the shadow and the resize border composeFrame() only forced the
alpha channel, so the buffer the driver reallocated after a size change was
presented as it is, which showed up as a black frame on every resize step.
The content is now always painted from the cache and only the shadow itself
is skipped when there are no margins.

The setting is named simple-window and means the opposite of the previous
shadow-and-border: it is off by default, so the window keeps its shadow and
the outer border for resizing.
2026-10-10 12:23:42 +03:00
alexei-zebra
ab7f542d61
Add display settings for the wayland window frame
The frame the native wayland backend draws gets three switches in the
display tab: a narrow 24px bar instead of the 48px one, the shadow with
the outer resize area, and redrawing the content while the window is
resized (off keeps the previous behaviour of stretching the last frame).

The settings are applied at runtime: the bar geometry is rebuilt and the
surface is resized together with the toplevel geometry, no restart needed.
The narrow bar drops the insets and the gap of its controls, so that they
sit flush against the window edge.

The switches are hidden outside of the wayland backend, which reports its
name through Window::getBackendName().
2026-10-10 12:23:42 +03:00
alexei-zebra
01ed8b7dc5
Fix 2D batch drawing with a stale texture binding
Batch2D cached the bound texture and skipped the bind when the cache
matched, but the render pipeline binds textures of its own and leaves a
non-zero texture unit active. A rectangle drawn without a texture (the
hud hotbar background and slot tiles) was then modulated by whatever
texture was left bound, which made the hotbar darken for a single frame
on every window resize.

The batch now draws from texture unit 0 and compares the cached texture
with the actual binding instead of trusting the cache.
2026-10-10 12:23:42 +03:00
alexei-zebra
543cab9579
Drop the manual trigger from the Windows workflow 2026-10-10 12:23:42 +03:00
alexei-zebra
b5416d1219
Fix the issues found while reviewing the Wayland frame work
A review of the branch turned up a number of defects, gaps and leftovers;
this commit addresses all of them.

Defects:
- the shadow uniform array held seven entries while eight locations were
  written, so the last one landed outside the object;
- CursorShape::LAST stayed in the middle of the enum after the new corner
  shapes were appended, which made the GLFW cursor table read out of
  bounds; the extra shapes are now mapped onto the ones GLFW knows, and
  the table is only filled for those;
- GlStateGuard asked glIsEnabled for an attribute pname, so it always got
  GL_INVALID_ENUM and never restored the vertex attribute arrays;
- the early returns in wayland_window_initialize left the global window
  and input pointers dangling when falling back to GLFW;
- the icon textures were listed nowhere, so none of them ever loaded;
- a shader failure disabled the shadow after the surface had already been
  sized for it, and VOXEL_DECORATIONS outlived the switch cleanup.

Behavior:
- the keyboard now releases every pressed key when it loses focus, and a
  repeat rate of zero means no repeat;
- the fourth UTF-8 lead byte is decoded with the right mask, control
  characters no longer reach text fields, and a vanished clipboard offer
  clears the cached text;
- compositor side decorations disable ours again instead of leaving two
  titles, the window destructor releases the rest of the state, and the
  content inset is computed before the GUI acts so the HUD and the
  container never disagree for a frame; the HUD clamps it;
- the window controls fall back to minimize, maximize and close, and the
  icons are drawn from textures only.

Cleanups: one monotonic timer instead of three, one vertex shader shared
by both renderers with a link check, one button layout parser, the inset
rule moved into Screen, the scissor stack moved into the base Window
(about 110 duplicated lines), named shadow and evdev constants, trimmed
includes, a README note about the Wayland dependencies, and the long
lines introduced by this branch wrapped.
2026-10-10 12:23:42 +03:00
alexei-zebra
c269d6efb3
Give the Wayland window an Adwaita-like frame
The engine-drawn title bar grew to 48 px with 24x24 window controls,
12 px away from the edge and from each other, all sharing one hover
highlight. The controls use textures now (gui/cross, gui/minimize_w,
gui/maximize_w and gui/restore_w when maximized) with the vector icons
kept as a fallback, and the title is centred in the bar, clamped to the
free space between the button groups.

The bar now sits inside invisible margins that carry a drop shadow, so
the window is resizable from outside the visible frame: the surface is
content plus twice SHADOW_MARGIN and xdg_surface.set_window_geometry
tells the compositor which part is the window. The shadow follows
Adwaita's window shadow: a Gaussian blur of 7 px (sigma 3.5) expanded by
1 px, rgba(0,0,0,0.5) focused and 0.3 in the backdrop, plus a 1 px
hairline, symmetric on all four sides - a 16 px wide frame would show a
fatter tail than the reference. Margins exist only while the window is
decorated by us and not maximized or fullscreen.

The engine composes the frame itself: it renders exactly as before, then
the backend copies the frame into a texture, clears the surface, draws
the shadow and puts the content in place with alpha forced to 1, which
keeps the frame opaque without touching a single render pass. Only
frames the engine actually drew are cached, and the EGL window is
resized before its surface size is asked for, so no frame is composed
from a buffer the compositor just replaced - that was the one frame
blink after a resize.

Resize cursors match GNOME: directional shapes for edges and corners
(w/e/n/s/ne/nw/se/sw) instead of the double-headed diagonals, with the
extra CursorShape values appended so the existing GLFW indices stay.

Measured: window 1123x751 opens as saved, fullscreen round trip returns
the same size with the settings untouched, the shadow alpha profile is
0.20/0.10/0.03 at 1/4/7 px from the edge against Adwaita's 0.21/0.095/
0.055, all four sides equal, menu layout baseline unchanged (706),
no errors in the log.
2026-10-10 12:23:41 +03:00
alexei-zebra
6c2192b5d8
Draw the window title bar by the engine
The native Wayland backend had no window controls: no title, no close
button, no way to move or resize the window, and the fullscreen toggle
could throw the window to another monitor. GNOME does not implement
zxdg_decoration_manager_v1, so there is nobody to draw a frame for us:
the backend now falls back to its own decorations when the compositor
offers no server side ones, and the engine draws the visible part.

The bar itself is drawn by the engine (WindowBar.cpp) through the usual
batch and font, so it uses the same assets as the rest of the UI and the
backend only owns the behaviour: hit zones, cursor shapes, click
interception and the xdg-shell requests. Its geometry follows the
desktop's button layout, read and subscribed through
xdg-desktop-portal over sd-bus (libsystemd is an optional dependency,
gsettings is only a startup fallback).

Controls behave like they do elsewhere:
- pressing anywhere on the bar starts a move once the pointer leaves a
  5 px radius, so dragging works from the buttons as well;
- a button acts on release, only if the pointer stayed on it;
- a double click on the bar toggles maximize;
- the top edge and the top corners resize, the top 8 px of the sides,
  the sides and the bottom are 8 px wide resize strips;
- right and middle clicks and the scroll wheel over the bar never reach
  the game.

The in-game user interface is offset below the bar while menus keep the
whole window, so the translucent bar shows the menu background through
itself and never covers the HUD. The HUD lays its elements out against
the content height and the cursor is translated once, which fixes items
following the mouse one row above the pointer in game.

The window size is now written to the settings when the window is
resized in windowed mode and applied on the first configure, so the
window opens with the size it was left with, and leaving fullscreen or
borderless mode restores it instead of overwriting the settings with the
fullscreen size (an unconditional unmaximize made the compositor restore
the maximized geometry).

Measured: menu layout unchanged (706 bright pixels in the same place),
gui viewport 1123x751 in menus against 1123x721 in game, 1123x751 ->
2560x1080 -> 1123x751 round trip keeps the settings, a saved 1000x640
opens as 1000x640, no errors in the log.
2026-10-10 12:23:41 +03:00
alexei-zebra
4731ac0706
keep the window framebuffer opaque
Both backends asked for an alpha channel (GLFW defaults to 8 alpha
bits, the Wayland EGL config requested 8), so everything the engine
draws with alpha - the UI panels, the water post effect - lowered the
window's own alpha and the compositor blended the desktop through it.
Visible on wine/Proton, where the whole window is composited.

Both now ask for an opaque framebuffer: GLFW_ALPHA_BITS 0, and
EGL_ALPHA_SIZE 0 with a fallback to an alpha config if the driver
provides none. Checked the result through the back buffer attachment:
alpha size is 0 on Wayland and on X11.
2026-10-10 12:23:31 +03:00
alexei-zebra
918051cd5d
allow running the Windows build manually
The workflow only ran for pushes to main/release and for pull requests,
so a topic branch could not be built without opening a pull request
first.
2026-10-10 12:23:31 +03:00
alexei-zebra
d9794afa67
read the clipboard asynchronously
getClipboardText() used to open a pipe, ask the selection owner for
the text and poll it with a 500 ms deadline, so every paste blocked the
UI thread (TextBox calls it directly) and a slow owner meant a visible
hang.

The selection is now fetched in the background: when the selection
changes, the backend requests the text into a non-blocking pipe and
getClipboardText() only returns the buffer, which the event loop fills
in as the data arrives. Pasting no longer blocks, and a source that
never answers simply leaves the previous buffer in place.

Also clears the advertised MIME list when a new selection offer
arrives, so a request is never made with MIME types of a previous
owner.
2026-10-10 12:23:31 +03:00
alexei-zebra
6a5e485bca
drop the environment switches
The backend, decoration and resize-logging switches were only used
while working on this, and undocumented ones should not stay:

- VOXEL_WINDOW_BACKEND: the backend is still chosen by WAYLAND_DISPLAY,
  and GLFW is used when it is not set;
- VOXEL_DECORATIONS: own decorations are always enabled when the
  compositor provides none;
- VOXEL_LOG_RESIZE: the resize statistics are removed together with the
  counters they needed.

WaylandDecorations.cpp replaces WaylandBar.cpp: drawing moved to the
engine, the file only holds the decoration behaviour now.
2026-10-10 12:23:31 +03:00
alexei-zebra
1dbd445027
give Window::getTitle a default implementation
Keeps the interface non-breaking for other window backends: the
decoration height and hovered button already have defaults, and now so
does the title.
2026-10-10 12:23:31 +03:00
alexei-zebra
14fa7e5fd2
fix building without the Wayland backend
The backend sources live in window/wayland and were picked up by the
global source glob, so a build with VOXELENGINE_WAYLAND=OFF (and any
non-Linux build, where the option is skipped entirely) tried to compile
them and failed on the generated protocol headers.

They are now collected separately and added to the target only when the
backend is enabled.

Also restores the CRLF line endings of Engine.cpp, GUI.hpp and
input.cpp, which were rewritten with LF and made their diffs look like
whole-file rewrites.
2026-10-10 12:23:31 +03:00
alexei-zebra
3b337241f5
draw window decorations with the engine GUI
The bar used to be drawn by the Wayland backend with its own shader,
bitmap font and textures, straight into the engine's GL frame. That
leaked GL state (the batch caches bound textures, so the engine kept
sampling the backend texture and all text turned into solid white
rectangles) and it duplicated fonts and styling.

Now the backend only owns the behaviour: hit zones, cursor shapes,
click interception and the compositor requests (move, resize,
minimize, maximize/restore, close). The bar itself is drawn by the
engine in WindowBar.cpp through the regular Batch2D/Font path, so it
looks like the rest of the UI.

Window gained getTitle(), getDecorationHeight() and
getDecorationHoveredButton(); GLFW keeps the defaults, so X11 and
Windows are unaffected. The backend's decoration drawing (bitmap font,
shader, quad batches) is removed: WaylandBar.cpp went from 630 to 140
lines.

Fixes found while debugging:
- GlStateGuard was defined but never used after the file split, so the
  stretched frame left its texture bound and broke text rendering after
  a window mode change; it is now applied around the cache capture and
  the stretched frame;
- takeScreenshot() now reads the front buffer and restores the read
  buffer afterwards.
2026-10-10 12:23:18 +03:00
alexei-zebra
b934e033b3
split the rest of the Wayland backend
WaylandWindow.cpp kept the window class with all methods defined in
place, the decorations, the free event listeners and the initialization
in one file. Now:

- WaylandWindow.hpp: the class declaration;
- WaylandWindow.cpp: surface, EGL, resize and frame pacing;
- WaylandBar.cpp: the window decorations (bar, font, buttons, dragging,
  edge resizing);
- WaylandListeners.cpp/.hpp: the free Wayland event handlers;
- WaylandInit.cpp: wayland_window_initialize.

No functional change.
2026-10-10 12:23:18 +03:00
alexei-zebra
cf92ebba76
split the Wayland backend into files
WaylandWindow.cpp held the protocol bindings, the shared compositor
state, the input implementation, the window itself, the free event
listeners and the initialization code in one 2400-line file.

Moved out of it:
- WaylandCommon.hpp/.cpp: shared compositor state, the display event
  loop, keysym mapping and the window logger;
- WaylandInput.hpp: the input implementation (keyboard, clipboard,
  cursors, key repeat).

No functional change.
2026-10-10 12:23:18 +03:00
alexei-zebra
1e689e88b1
add native Wayland window backend
Wayland support was missing a proper windowing layer: the GLFW backend
leaves the known platform gaps (cursor themes, window icon, window
position, fullscreen output selection).

The new backend talks to the compositor directly:
- xdg-shell, EGL, xkbcommon (keyboard, repeat, layout) instead of GLFW;
- cursors through wp_cursor_shape_manager_v1, so no cursor theme lookup
  is required and no "standard cursor shape unavailable" errors appear;
- window icon and title are drawn by the engine itself, since Wayland
  has no window icon protocol and GNOME provides no server-side
  decorations;
- fullscreen requests the current output (set_fullscreen with NULL), so
  the window no longer jumps to another monitor;
- interactive resize presents a cached frame scaled to the new size
  while the pointer is down and refreshes the real frame when the drag
  pauses, keeping the window glued to the cursor.

libdecor is not used: libdecor_frame_commit() redraws the whole
decoration and acks the configure in the same call, and mutter sends
200-330 configures per second during an interactive resize, so the
decoration was redrawn hundreds of times per second (measured: 2 s of
work per second, loop stalls up to 6 s). The decorations are drawn by
the engine instead, which measured 2.3 ms average configure-to-present
latency during a real drag.

GLFW stays the backend for X11 and Windows; VOXEL_WINDOW_BACKEND=x11
forces it on Wayland sessions.
2026-10-10 12:23:18 +03:00
MihailRis
1dd1af1a72
Merge pull request #1023 from MihailRis/remove-incorrect-fix
remove incorrect fix
2026-10-10 12:11:43 +03:00
MihailRis
521ebf43ab remove incorrect fix 2026-10-10 11:36:31 +03:00
MihailRis
f036979dc0
Merge pull request #1007 from Astazium/ui-fixes
ui fixes
2026-10-10 11:34:34 +03:00
MihailRis
7130a62593
Merge pull request #1022 from MihailRis/rename-voxelengine-to-voxelcore-in-cmake
complete the rename of voxelengine to voxelcore
2026-10-10 11:27:37 +03:00
MihailRis
8962042627 complete the rename of voxelengine to voxelcore 2026-10-10 10:54:36 +03:00
MihailRis
a875630cd8
Merge pull request #1021 from DIvan2K/main
flake.nix fix program filename
2026-10-10 10:47:23 +03:00
MihailRis
50de0afb62
Merge pull request #1019 from ostermine/fix/reload-module-env
fix reload_module ignoring pack environment
2026-10-10 10:42:59 +03:00
DIvan2000
a2321e0e28 fix program filename 2026-10-10 05:04:14 +04:00
ostermine
d8017ff995 fix reload_module ignoring pack environment
reload_module loaded the new module code with the global environment,
while require runs modules in their pack environment. After reload,
PACK_ID and other pack globals were nil in the module.
2026-10-10 00:52:23 +03:00
MihailRis
e8a83423d8 fix outdated doc/*/scripting/builtins/libgfx-skeletons.md
Some checks failed
x86-64 AppImage / build-appimage (ubuntu-22.04) (push) Has been cancelled
Build / Build (push) Has been cancelled
Macos Build / build-dmg (push) Has been cancelled
Windows Build (CLang) / build-windows (clang, windows-latest) (push) Has been cancelled
MSVC Build / build-windows (windows-2022) (push) Has been cancelled
2026-10-09 00:09:48 +03:00
MihailRis
05c0a1868d
Merge pull request #1014 from MihailRis/patch-0.32.2
Some checks are pending
x86-64 AppImage / build-appimage (ubuntu-22.04) (push) Waiting to run
Build / Build (push) Waiting to run
Macos Build / build-dmg (push) Waiting to run
Windows Build (CLang) / build-windows (clang, windows-latest) (push) Waiting to run
MSVC Build / build-windows (windows-2022) (push) Waiting to run
0.32.2 patch
2026-10-07 23:31:28 +03:00
MihailRis
5060a8635d fix locked cursor if world was closed with menu hidden 2026-10-07 23:09:40 +03:00
MihailRis
cf35023adf fix 'mouse:' input prefix is not available 2026-10-06 12:53:50 +03:00
MihailRis
99a62710b8
Merge pull request #1013 from MihailRis/patch-0.32.1
Some checks failed
x86-64 AppImage / build-appimage (ubuntu-22.04) (push) Has been cancelled
Build / Build (push) Has been cancelled
Macos Build / build-dmg (push) Has been cancelled
Windows Build (CLang) / build-windows (clang, windows-latest) (push) Has been cancelled
MSVC Build / build-windows (windows-2022) (push) Has been cancelled
0.32.1 patch
2026-10-05 23:18:48 +03:00
MihailRis
cdc32173c3 update doc/*/xml-ui-layouts.md 2026-10-05 22:26:04 +03:00
MihailRis
76e5e5b6f8 fix vca 'configure' directive parsing 2026-10-05 22:11:21 +03:00
MihailRis
446b6edd03 update doc/*/scripting/ecs.md 2026-10-05 21:57:16 +03:00
MihailRis
3c7755f61b fix 'selectable' with static entities 2026-10-05 21:39:18 +03:00
MihailRis
ef85592e21 fix chunks render limits 2026-10-05 21:21:33 +03:00
MihailRis
09b427be1e
Merge pull request #1011 from ostermine/docs/readme-openssl
Some checks are pending
x86-64 AppImage / build-appimage (ubuntu-22.04) (push) Waiting to run
Build / Build (push) Waiting to run
Macos Build / build-dmg (push) Waiting to run
Windows Build (CLang) / build-windows (clang, windows-latest) (push) Waiting to run
MSVC Build / build-windows (windows-2022) (push) Waiting to run
docs: add OpenSSL to Linux build dependencies in README
2026-10-05 19:15:04 +03:00