SPrismLauncher works great for testing
Salacritty should work too
Nweston clients
Nthey only run on wayland
Tyep i just checked
OOK! The terminal shows up and I can see the window and the control widgets and such, but when I turned on my controllers to try to use it, they didn't show up. Does it not support hotplug?
O(restarted to get it to register controllers) The window is pretty hard to grab and use, or at least unintuitive.
Smonado doesn't support hotplug, you have to turn your controllers on before starting monado
OWhat is the control on the bottom center of the window? I don't see a tool tip or label.
OOh, when will that be fixed?
Sidk, i don't work on monado and idk if that is even something that is being worked on
Nwhat do you mean
Nit's for panel shells, basically you can take 2D apps and put them in different 3D objects to interact differently
OI was expecting to be able to palm-grab to move the window around without resizing it, like I can in resonite, and trying to grab the controls on the corners by pointing an arrow at it which isn't a laser and then doing a grab gesture on the opposite side of the hand was weird. Splitting the difference between a fairly intuitive gesture control of "point at the thing and do a grab gesture to grab it remotely" and "actually grab the thing at the position to grab the thing" with "do a grab gesture at the position, but the active space of the grabbing isn't where the grab gesture occurs but where a pointer indicator is" and it didn't feel good to me.
OWhat's the current story for typing in Stardust like? Do I need to swap back and forth between keyboard and controller like I did in simula before?
Noh shoot i didn't see this
Nhaven't added software keyboards yet, am working on it
Nit's... taking a while
Sis there still any interest in porting the stardust server to bevy? if yes i will try to integrate smithay with bevy
Nyes, somewhat... but idk if i can integrate it well
Salso completely unrelated, is there a reason why you are doing automatic material batching instead of using something like material handles?
Nbecause i want the api to be as simple and render pipeline agnostic as possible and also because i want to batch materials across client instances
Sah, okay, fair enough
NSegl on nvidia strikes again...
Nit's the fence again
N@Pandapip1 did that person patch monado with this? https://cdn.discordapp.com/attachments/1083091622880890880/1277856820056035338/nvidia_egl_fence_wait.patch?ex=6728ff27&is=6727ada7&hm=42ce1aa1cc31461e11b4a3e5a174e7feca6126876a40860e28333e8010925b24&
PI don't think that patch is in nixpkgs. I can very quickly add that and see if it works.
SI have a slightly better one, also put it behind a flag or something like that since it's more of a hack than a fix
Nsure thing :D
Sthis is the newer patch
Nooh
Shm?
Njust it's only 1 line
Syeah, but one line that breaks fences, just that on nvidia they are broken already so it shouldn't make much of a difference, and since it breaks fences for every gpu i don't want to upstream that
N@Schmarni is flatland going well?
SIt still doesn't have input, i can work on it rn tho
Ncool, lemme know if you've got any questions
Sone issue i have is that if i make the hover plane a child of the surface element it doesn't get resized, the only way around that that i can think of rn is using a channel which i have to insert into self
Noh... you're not resizing it by scaling it right?
Nwhy not just store the size from the resize handles in the state struct then generate the UI for the hover plane from that size?
Sit is strored in
ToplevelInfo which is stored in ToplevelState but build is not run after a state change, or maybe it's that create_inner is not called again, maybe i just need to handle updates correctlyNyeah it sounds like it's not updating right
Nyou have to manually check for updates in
updateNso, compare
self.size != old.size or such then if not you call the update size methodNcreate_inner is only called once, when you first create the elementSyep, i just forgot to update it
Ncool
Sshould i store touch inputs in the state or should i use events like the resize handles?
Ni'd recommend events, that way we can put the touch plane input back into the asteroids library for use in other stuff too