I take my shitposts very seriously.

  • 30 Posts
  • 1.73K Comments
Joined 3 年前
cake
Cake day: 2023年6月24日

help-circle
  • From a purely profit-oriented perspective, no. They’re setting up a pretext to eliminate the lifetime license plan due to a lack of interest. No sane person would pay that kind of lump sum for the service (and the insane ones will bring in triple the revenue), so they’ll claim that there is no market for it. After that, they’re free to crank up the periodic subscription prices.

    Never attribute to stupidity that which is adequately explained by profiteering opportunism.






  • Yes, it’s recognised as a controller both in non-Steam games and in other applications like KDE Settings. It works just like any other controller with the usual, quasi-standard inputs (analog sticks, face buttons, etc). Steam support regarding non-Steam games:

    Everything should work as intended if you have purchased and launched your game directly through Steam, but in many cases you will also be able to use the Controller with non-Steam games that run independently.

    I’ve heard the argument that it is recognized as a KBM if you’re not on Steam.

    If Steam isn’t running and there are no other games that capture the controller input, the SC enters “lizard mode” where it emulates mouse and certain keyboard inputs. The right touchpad becomes a mouse, the left touchpad becomes a scroll wheel, R2 is left click, L2 is right click, A is Enter, B is Escape; wev displays the correct input events. Lizard mode is disabled when you launch a game.

    (edit) It sounds like this only works in Linux. Windows needs a separate utility to use the SC with non-Steam games.

    (edit 2) This is what KDE reports:

    It can detect the back buttons (Paddle 1-4) and the quick access menu (Miscellaneous). hid-recorder also shows that all other inputs are also available through the /dev/hidraw* device. I wouldn’t be surprised at all if someone released a standalone Steam Input emulator app within a few weeks.






  • XDG Desktop files are a mostly standardized way to integrate individual programs into the desktop. For example, a desktop file in /usr/share/applications or ~/.local/share/applications can add programs to the application launcher, both desktop launcher menus and separate apps like dmenu-run; or they can be used to start applications when the desktop session starts by placing them in ~/.config/autostart.

    Desktop files can also set properties related to an application. In this particular case, the MimeType field tells the desktop session what MIME types should be associated with the application. For example, my desktop file for Blender associates the application/x-blender MIME type with it, which causes Blender to show up in the Open with… dialog.

    The MimeType field is a semicolon-separated list. One desktop file can define multiple associated MIME types for the same application. Krita instead creates a separate file for each association.