<waddlesplash>
hmm there's actually a case here where we disable_interrupts and never reenable them
<waddlesplash>
that should be acceptable because they should never be enabled in the first place here...
<waddlesplash>
hmm, or maybe not, perhaps "end_of_interrupt" can reenable interrupts?
x10z has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<waddlesplash>
well either way, I wouldn't know what the problem could be without a reproduce case and a KDL backtrace. and it could be something else entirely
aakashi2001 has joined #haiku
aakashi2001 has quit [Read error: Connection reset by peer]
matt__ has joined #haiku
frkazoid333 has joined #haiku
frkzoid has quit [Ping timeout: 480 seconds]
x10z has joined #haiku
matt__ has quit [Ping timeout: 480 seconds]
<x512[m]>
waddlesplash: User suspect hrev56274. hrev56272: OK, hrev56276 and hrev56278: broken (app freezes.
x10z has quit []
frkzoid has joined #haiku
frkazoid333 has quit [Ping timeout: 480 seconds]
<waddlesplash>
x512[m]: yes, that's the scheduler commit. again I need a KDL trace.
frkzoid has quit [Read error: Connection reset by peer]
frkzoid has joined #haiku
<x512[m]>
waddlesplash: It need to wait until this happens for person able to use KDL.
<Begasus>
PulkoMandy, gertty launches ok here on 32bit
brass has joined #haiku
frkzoid has joined #haiku
frkazoid333 has joined #haiku
matt__ has quit [Ping timeout: 480 seconds]
frkzoid has quit [Ping timeout: 480 seconds]
Begasus_32 has joined #haiku
krbtgt has joined #haiku
mmu_man has joined #haiku
<andreasdr[m]>
Good morning
<PulkoMandy>
Begasus, did you create a config file? it launches ok when there isn't one, but after creating it, it crashes for me. But maybe it's x86_64 only
<kodaloid>
what happens if the window is close to the right side of the screen, does it adjust accordingly?
<x512[m]>
PulkoMandy: Unnecessary complexity.
<PulkoMandy>
yes, just like other menus it will open in a place that makes sense
Major_Biscuit has joined #haiku
<x512[m]>
It also should be possible to set some manual numbers for resolution.
<kodaloid>
think the last time I saw that kind of menu was in the 90s with the winamp vis preset picker, could work in some situations, but I think there is a reason we don't see it more often.
<x512[m]>
And highlight native/preferred resolution if known.
ynhuser|828468 has joined #haiku
<PulkoMandy>
you can set custom resolutions from the command line using the screenmode command
thomaslewis has left #haiku [#haiku]
pinaraf has quit [Ping timeout: 480 seconds]
geist has joined #haiku
Major_Biscuit has quit [Ping timeout: 480 seconds]
stickman68 has joined #haiku
<x512[m]>
Why force using command line? Haiku is not Linux.
<x512[m]>
Screen preference also allows to automatically restore from wrong resolution.
<kodaloid>
tbf custom resolutions in the system ui is not exactly supported on windows/macos either
<kodaloid>
usually left up to the graphics driver to provide that kind of feature
matt__ has joined #haiku
frkzoid has quit [Ping timeout: 480 seconds]
<ermo[m]>
<x512[m]> "Why force using command line..." <- I think being able to both is useful.
<ermo[m]>
There's value in being able to script schanges too
<ermo[m]>
from the "have a back-end that suports both scripted changes and GUI changes" perspective I mean
<x512[m]>
Yes and that mean GUI option should be also present.
<ermo[m]>
one doesn't have to negate the other
<ermo[m]>
ok, then it sounds like we agree.
<ermo[m]>
on Linux/Xorg, you can add custom resolutions with xrandr and then select them in the GUI.
<ermo[m]>
which implies that it might be possible to do it all from a gui too
<ermo[m]>
width (pixels), height (pixels), refresh rate, reduced blanking -> add mode to list of selectable modes
<ermo[m]>
and use the CVT algorithm
<ermo[m]>
(if this is all obvious, I apologise)
_orealis has joined #haiku
orealis has quit [Ping timeout: 480 seconds]
_orealis is now known as orealis
<x512[m]>
On Haiku mode list is provided by driver and not configurable if I am correct.
<x512[m]>
Some progress in making Haiku serverless Wayland applications support:
<Not-34b6>
[haiku/haikuwebkit] carlosgcampos f2bacb5 - The script webkit-filter-log is broken since the github migration
<Not-34b6>
[haiku/haikuwebkit] shallawa c5d5c98 - ImageBuffer subclasses should not be templates
<Not-34b6>
[haiku/haikuwebkit] youennf 82a9cba - [ Mac EWS ] imported/w3c/web-platform-tests/workers/semantics/multiple-workers/004.html is a flaky text failure
<Not-34b6>
[haiku/haikuwebkit] ... and 271 more commits.
thomaslewis has joined #haiku
<Anarchos>
what is the library to link with if my sources are compiled with -pg, generating some "extern _mcount" symbols ?
thomaslewis has left #haiku [#haiku]
humdinger has joined #haiku
thomaslewis has joined #haiku
Yonle has joined #haiku
thomaslewis has left #haiku [#haiku]
thomaslewis has joined #haiku
frkzoid has joined #haiku
stickman68 has quit [Read error: Connection reset by peer]
matt__ has quit [Ping timeout: 480 seconds]
matt__ has joined #haiku
blevins has joined #haiku
thomaslewis has left #haiku [#haiku]
frkzoid has quit [Ping timeout: 480 seconds]
frkazoid333 has joined #haiku
thomaslewis has joined #haiku
thomaslewis has left #haiku [#haiku]
frkzoid has joined #haiku
yiiwna has joined #haiku
matt__ has quit [Ping timeout: 480 seconds]
thomaslewis has joined #haiku
frkazoid333 has quit [Ping timeout: 480 seconds]
thomaslewis has left #haiku [#haiku]
<waddlesplash>
x512[m]: the problem is, there are more than one major implementation of the Wayland client
<waddlesplash>
many more serious applications don't use libwayland but some other library which wraps the protocol
<waddlesplash>
and Wayland itself isn't that great of an API, imo
<x512[m]>
For example?
<x512[m]>
What applications do not use libeayland-client?
<x512[m]>
libwayland-client
matt__ has joined #haiku
<x512[m]>
Wayland is terrible API, but it is simple and allow quick and stable port of GTK 3+.
<waddlesplash>
huh? we already have GTK3 using Xlibe?
zdykstra has quit [Server closed connection]
<waddlesplash>
why work on this?
itanium686 has quit [Quit: Vision[]: i've been blurred!]
zdykstra has joined #haiku
<waddlesplash>
anyway I can't recall ATM what other implementations of Wayland clients there are but I remember running into some major apps that used them
<x512[m]>
GTK3 with Xlibe is quite buggy.
<x512[m]>
And GTK developers are planning dropping X11 support.
systwi has quit [Server closed connection]
systwi has joined #haiku
<x512[m]>
It is also much easier to get OpenGL/Vulkan support for Wayland compared to xlib/xcb. xlib have complicated GLX API.
frkzoid has quit [Ping timeout: 480 seconds]
<waddlesplash>
x512[m]: I've heard it suggested the bugs may be due to Cairo code not really being tested without Xrender.
<waddlesplash>
so I'd suggest spending some time implementing XRender, or more closely debugging invalidation events
<waddlesplash>
x512[m]: they are discussing dropping it, they aren't going to do it for some time, and it'd only be on gtk5 probably
<x512[m]>
For Wayland wl_surface_commit can be just mapped to BView::Invalidate/DrawBitmap and no glitches.
<waddlesplash>
seeing as nothing even uses gtk4 then I don't know if it matters yet
<waddlesplash>
again: why not try working on XRender?
<waddlesplash>
the fact is that input events are a HUGE pain to get working correctly no matter what toolkit you use
<x512[m]>
XRender is obsolete and really terribly designed. It have no polygon support and use trapezoids instead.
humdinger has quit [Quit: Vision[]: Oi with the poodles already!!]
<x512[m]>
For Wayland input events seems easy to implement.
<waddlesplash>
so even if your system has less glitches with graphics you are going to encounter tons of issues with input events
frkzoid has joined #haiku
<waddlesplash>
yes, "seems"
<waddlesplash>
x512[m]: can you at least open source your work on graphics drivers before tackling another project maybe?
<x512[m]>
Just translate Haiku codes to input-event-codes.h.
<waddlesplash>
yes, it sounds simple, in fact Haiku events already map easily on to X11 events too
<waddlesplash>
but then you have to factor in things like mouse grabs
<x512[m]>
waddlesplash: About graphics driver: you have not answered before do you find that code useful if it don't support your hardware?
<waddlesplash>
x512[m]: I already looked into GLX and think it's possible to implement in Xlibe and was planning to do do
<x512[m]>
What do you plan to do with code?
<waddlesplash>
well, there's other users who find it useful, and maybe I could look at adding support for my hardware?
<waddlesplash>
either way it's a bit annoying that you post these screenshots of clearly working things, even if they're a bit rough, and then ... no way to actually use them
<x512[m]>
Because I can't yet found users that have compatible GPU and able to compile/install/run driver.
gouchi has quit [Remote host closed the connection]
<waddlesplash>
x512[m]: also I fixed a bunch of invalidation bugs and this improved things in GTK recently, but I didn't release it yet. I think if someone takes the time to actually debug how Cairo processes invalidation events then the glitches can be fixed
frkazoid333 has joined #haiku
<waddlesplash>
GTK3 just uses "draw bitmap" to draw to the screen too, you know
<waddlesplash>
on X11 I mean. so the bugs are probably in invalidation event handling or something and are probably fixable
<waddlesplash>
whatever ones there are remaining, it seems they're related to lots of invalidation occuring quickly
<rennj>
stupid tor-browser needs like wayland...and mozilla doesnt
<x512[m]>
For Mesa OpenGL I plan to use EGL only and drop HGL. And implement HGL as wrapper over EGL in glvnd.
matt__ has quit [Ping timeout: 480 seconds]
<waddlesplash>
okay, well it doesn't matter, I was going to implement GLX using BGL either way
<rennj>
fix to getting tor-browser running on older x11 box
<x512[m]>
BGLView is very limited and it do not support important features like setting required OpenGL API version or creating multiple contexts.
<waddlesplash>
x512[m]: also some things like IME support or clipboard support are not easy to do on Wayland because you have to implement so many extension protocols
<tqh>
wayland makes a lot more sense than X to me, as X seems to be more or lessa abandoned.
<rennj>
redhat said its done with x11
<waddlesplash>
x512[m]: meanwhile I already implemented most of what's needed for the clipboard and there's stubs for ime
<rennj>
and they were maintaining it
<rennj>
see what bsd and solaris folks do
<rennj>
maintenance mode
thomaslewis has joined #haiku
<x512[m]>
For libwayland-client I want to add add-on system that will handle
<x512[m]>
handle client requests instead of server process.
<x512[m]>
So no sockets and fd.
frkzoid has quit [Ping timeout: 480 seconds]
<x512[m]>
waddlesplash: The lack of proper communication is real problem.
frkzoid has joined #haiku
matt__ has joined #haiku
thomaslewis has left #haiku [#haiku]
stickman68 has joined #haiku
<stickman68>
Hey
<waddlesplash>
x512[m]: what do you refer to?
<x512[m]>
waddlesplash: GTK have invalidation bugs (black flickering) on X11 even in Linux. Developers don't cake X1w backend anymore.
<x512[m]>
care X11
<waddlesplash>
GTK3 or gtk4?
<x512[m]>
GTK4 I think.
<x512[m]>
X11 have no proper invalidation control.
<x512[m]>
Haiku libwayland implementation can use BView::SetViewBitmap.
frkazoid333 has quit [Ping timeout: 480 seconds]
HaikuUser has joined #haiku
<x512[m]>
Wayland usually use double buffer flipping.
x10z has joined #haiku
<waddlesplash>
x512[m]: no, there's XSync
frkzoid has quit [Ping timeout: 480 seconds]
<x512[m]>
XSync seems related to protocol queue, not repainting.
<x512[m]>
For Wayland handling repaint event is not needed at all.