203
How? (sh.itjust.works)
submitted 1 year ago by to c/linuxmemes@lemmy.world
112 comments fedilink hide all child comments
 

Does anybody know how to set a window always on bottom in rust gtk4? set_type_hint() does not exist.

you are viewing a single comment's thread
view the rest of the comments
[–] 163 points 1 year ago (40 children)

Linux gives users the freedom to keep using x11 :p

  • permalink
  • fedilink
  • source
  • hideshow 40 child comments
    •
  • [–] 98 points 1 year ago (30 children)

    They are even free to thanklessly maintain X11 for all the other contrarian fossils, because the developers sure aren't doing it anymore.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 30 child comments
    •
  • [–] 8 points 1 year ago (3 children)

    There's nothing contrarian in using software that works and and fulfills all your needs.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 6 points 1 year ago (1 child)

    I gladly accept the fossil label, but there's no contrarian sentiment behind it ... I just never felt any pain staying with X11.

    Also, the window manager I use is developed by a friend who lives 10min away and texts me every time he has an update, and I love it ... doesn't work on Wayland, though ...

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 4 points 1 year ago* (3 children)

    Wayland doesn't work for me, I rely on a tablet in lieu of a mouse and under Wayland it's unusable. I tried hard

    Under an X session it behaves flawlessly

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 1 year ago (2 children)

    Did you try it that with Gnome? I heard that some input methods suffered with the wayland transition because mutter makes some weird choices. From my personal experience, libinput works great with a wacom tablet, so I'm assuming you ran into an issue with a specific DE.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [+] -36 points 1 year ago* (last edited 1 year ago) (18 children)

    Keep angrily gaslighting. Surely you'll EVENTUALLY shame veterans who have been using Linux productively for decades into joining the cult of security over function.

    You come into MY home, into MY workflow, take features away from me that have been there ignoring all protests, then have the sheer unmitigated GALL to mock me when I dare to complain?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 18 child comments
    •
  • [–] 55 points 1 year ago (16 children)

    Dude, I am using Linux since 25 years.

    Just because you like it so much does not mean that anybody will maintain Xorg for you. Feel free to do it yourself.

    I chose Wayland. Not because security, but because I have a primary HDR ultrawide and an old secondary monitor.

    Running variable refreshrate does not work with this configuration on Xorg.

    HDR does not exist in Xorg.

    And never will be.

    Just keep in complaining just because someone points out that Xorg is dead.

    Xorg is dead! That is not gaslighting, this is a fact

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 16 child comments
    •
  • [+] -24 points 1 year ago* (15 children)

    I WILL continue to use Xorg. My workflow requires it. If that means I have to use an unmaintained window manager forever, so be it.

    None of this would be an issue if the Wayland developers weren't so pigheaded that they insist upon forcing their pure, untainted design philosophy onto the project rather than building an inclusive model that allows for backwards compatibility with the system it's meant to replace.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 15 child comments
    •
  • [–] 47 points 1 year ago (7 children)

    I will concede that not every obscure feature has been kept but the vast majority of users are now better served by wayland compositors. I have no idea what you mean by "project", but if they had no concerns for backwards compatibility, then XWayland wouldn't exist.

    Stopping work on X11 because it's been an unmaintainable mess for ages doesn't really count as "forcing" anything upon anyone. I won't pretend that Wayland protocol development hasn't seen plenty of disagreements, but it is still a collaborative process.

    Your disagreements seem fairly vague to me and I can't help but think that the "pigheaded" label is somewhat ironic, after your first paragraph.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 16 points 1 year ago

    There is currently one major Usecase that does not work yet with Wayland. Multiwindow positioning through the application.

    In science, and some stuff like KICaf or Gimp use this feature excessively. And as someones that relies on KiCad, it is a fucking pain.

    But, solutions are being discussed and implementations will follow

  • permalink
  • fedilink
  • source
  • parent
  • [–] 1 point 1 year ago (4 children)

    I am not better served. I am now in the quite new position where I'd have to rewrite some of my own personal software if i simply just decided to change DE

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 1 year ago (3 children)

    That sounds like a fairly niche problem to have.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 3 points 1 year ago (2 children)

    see that's the problem. Everyone's first response is that it's a niche problem. For every complaint. So what? It's a new problem is the point, however niche.

    Btw, this is not a niche problem. Some big projects have explicitly said they have had this very problem

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 1 year ago (1 child)

    Let me rephrase that: it sounds like a niche problem to have for an end user. It also doesn't sound like a fair complaint, because no long-term replacement to X was ever going to be drop-in the way you seem to expect.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 4 points 1 year ago

    I am not referring to it being a drop-in replacement. I'm referring to the fact that there are multiple supposedly-interoperable-but-not-really non-drop-in replacements is the problem. And it does affect the end user if devs find it difficult to adopt (as many do).

    Wayland is designed for ease of development for wayland designers. "We're just a protocol, the coding is left to anyone else" is the easiest way to write code. Because they decided not to write any at all.

  • permalink
  • fedilink
  • source
  • parent
  • [+] -6 points 1 year ago

    The "forcing" was in making Wayland shit, rather than replacing it with something with at least the same capabilities as X11 (even if they are now guarded by granular permissions).

  • permalink
  • fedilink
  • source
  • parent
  • [–] 25 points 1 year ago

    building an inclusive model that allows for backwards compatibility with the system it's meant to replace.

    That's honestly a terrible approach and defeats the porpoises. For example, screen recording. You can't be "backwards compatible" (aka any app can record at any time) and have them ask for permission (the honestly better way to go).

    Bear in mind, Wayland devs didn't force anything. They offered an alternative to X and the distros chose that after evaluating pros and cons.

    Pick a distro that aligns with your needs like we all do.

  • permalink
  • fedilink
  • source
  • parent
  • [+] 9 points 1 year ago* (last edited 11 months ago) (4 children)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 8 points 1 year ago (2 children)

    Not who you asked, but:

    • sxkhd: no global hotkey daemons allowed except the compositor

    • i3wm inside of xfce/plasma: every compositor is implemenyed as a monolithic DE, fuck modularity

    I still switched to Wayland, but can't be bothered to customise a new wm

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
    • load more comments (-1 replies)
  • [–] 6 points 1 year ago

    Noones going into your home and taking features away from you, they just decided they don't want to be putting a ton of effort into something 2 people care about.

    The beauty of FOSS is devs are free to make these decisions just like you're free to develop what you need.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 6 points 1 year ago (5 children)

    ugh I wish I could but my Laptop set up says "no, you can't." discrete Nividia GPU with onboard AMD GPU and gaming on x11 is a no go for me. So my only choice is wayland :/

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 2 points 1 year ago (2 children)

    Is it something specific to a particular model or combination of those? Because I run a laptop with amd integrated GPU and discrete nvidia GPU (not that rare, actually) and Wayland works flawlessly. Games use xwayland without any issues when necessary.

    I used to have my reservations a year or so ago, but Wayland has grown in leaps and bounds over the last couple of years. It is much more ready now.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago (1 child)

    yeah it works flawlessly on Wayland, that wasn't what I was saying. I'm saying on x11 it doesn't work for gaming because of the setup. Say I want to use I3 or Herbstfluftwm. If I open a game and ONLY stay on that game it's fine. but if I navigate away from it to look at a web browser or check discord and then toggle back to the game it results in a black screen or simply shows the desktop and the game is unresponsive. And from what I was able to find online the consensus seems to be it's because x11 doesn't play well with integrated and discrete dual GPUs.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 1 year ago

    Oh, my bad. Misread it the other way around. Disregard the comment then. That said. I disagree with the other commenter. Such a combination of GPUs is not rare at all. It was even recommended frequently to PC builders about 5+ years ago.

  • permalink
  • fedilink
  • source
  • parent