Announcement

Collapse
No announcement yet.

KDE Sees New Features, Bug Fixes Ahead Of Christmas

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
    polarathene
    Senior Member

  • polarathene
    replied
    ngraham
    Senior Member
    ngraham with the audio applet change, the tab bar was moved to the bottom for UX reasons? But is that dependent on where the applet/panel is positioned on the screen edge? On your blogpost one user shared the concern that it addresses a UX issue for some users by making it an issue for other users.

    Perhaps it makes sense as a default but could be configured/flipped when that suits better?

    Personally, I am rarely interacting with the tabs, so them being further away from the panel works well for me, and mute button was near my applet, but now will be all the way up with the header above the volume slider? (not complaining btw, it may not be a UX improvement for me but it's not a major inconvenience either). I assume the applet layout doesn't have context to adapt itself, this is probably a pattern that applies for most applet views, so consistency is more important

    I have a bottom panel, only one audio device usually and if there were any minor UX issue, I guess it's the amount of empty/blank space padding between the panel and the volume slider as it's unable to adapt based on height (not always a bad thing if audio devices are frequently changing and you want to have a fixed/predictable location for the slider, but otherwise blank space is contributing much?).

    Leave a comment:

  • tildearrow
    Senior Member

  • tildearrow
    replied
    Originally posted by Calinou View Post

    Does kwin-lowlatency help if you're not using compositing? I have a 144 Hz monitor but I always have compositing disabled (to get the best gaming performance). Being on Fedora 33, I'm wondering if it's worth the trouble to use kwin-lowlatency instead of stock KWin.
    It doesn't because you are not using compositing. kwin-lowlatency only helps with compositing performance.

    Leave a comment:

  • Vistaus
    Senior Member

  • Vistaus
    replied
    Originally posted by sa666666 View Post

    That's the way 'Datatypes' worked on the Amiga, many moons ago. You install a new Datatype, and all applications can immediately use it, without evening knowing how it works for adding specific code for it.
    They still do: even current AmigaOS versions support this still.

    Leave a comment:

  • ms178
    Senior Member

  • ms178
    replied
    Originally posted by Calinou View Post

    Does kwin-lowlatency help if you're not using compositing? I have a 144 Hz monitor but I always have compositing disabled (to get the best gaming performance). Being on Fedora 33, I'm wondering if it's worth the trouble to use kwin-lowlatency instead of stock KWin.
    You have to ask
    tildearrow
    Senior Member
    tildearrow who is the author. As there is a COPR repo for it, I'd say it is worth a try (see: https://github.com/tildearrow/kwin-lowlatency for details).

    Leave a comment:

  • R41N3R
    Senior Member

  • R41N3R
    replied
    Disman and KDisplay are much better than the Plasma counterparts KScreen/libkscreen. Just now when I installed a new system and I wanted to adjust the scaling on Plasma Wayland, there was no option to do that... well for whatever reason this is not always there (bug report exists). Then I switched to KDisplay and Disman. First it used a scaling that was already quite good to read and secondly it allowed me to change the scaling. From my point of view the Plasma devs should be more open to include the nice changes done for Disman and KDisplay.
    Regarding KWinFT, it's great to see how some of the fundamentals to be cleaned up and modernized. I just feel it would have been better to only focus on Wayland and remove X11 at this stage. Supporting both seems like a hugh amount of work and many users of KWin on X11 will probably not switch to KWinFT anyway. KWinFT on Wayland is not yet better than KWin Wayland for my use cases, but it seems that like the next release might be.

    Leave a comment:

  • bug77
    Senior Member

  • bug77
    replied
    Originally posted by Calinou View Post

    Does kwin-lowlatency help if you're not using compositing? I have a 144 Hz monitor but I always have compositing disabled (to get the best gaming performance). Being on Fedora 33, I'm wondering if it's worth the trouble to use kwin-lowlatency instead of stock KWin.
    Compositing can be toggled with a shortcut. Keeping it permanently disabled just to improve performance in games seems a little heavy handed.
    bug77
    Senior Member
    Last edited by bug77; 20 December 2020, 12:53 PM.

    Leave a comment:

  • uid313
    Senior Member

  • uid313
    replied
    Originally posted by sa666666 View Post

    That's the way 'Datatypes' worked on the Amiga, many moons ago. You install a new Datatype, and all applications can immediately use it, without evening knowing how it works for adding specific code for it.
    Yeah, really cool!

    Leave a comment:

  • sa666666
    Senior Member

  • sa666666
    replied
    Originally posted by uid313 View Post
    "With KDE Frameworks 5.78, all KDE software now supports AVIF (AV1) images when libavif is present."

    Wow, this is really cool. That all software can get support for more file formats when a library is installed without that software has to do anything. So you just install a image library and all image software now can handle that file, you install a audio format and all your media players can now handle that format, that's really cool.
    That's the way 'Datatypes' worked on the Amiga, many moons ago. You install a new Datatype, and all applications can immediately use it, without evening knowing how it works for adding specific code for it.

    Leave a comment:

  • f0rmat
    Senior Member

  • f0rmat
    replied
    Originally posted by ngraham View Post

    I'm familiar with the interpersonal and technical situation and would not characterize it this way. I have refrained from voicing my perspective publicly out of respect for Roman, because I think he does good work and I don't think anyone benefits when dirty laundry gets aired. But please do understand that every situation which looks simple on the surface is likely more complicated than it seems. There are rarely clear good guys and bad guys.
    Truly said....there are always three sides to every argument or discussion: one side, the other side, and the truth. Unfortunately, the truth side never seems to come out; but it can be protected by people who have honorable intentions. Nothing is ever achieved by airing dirty laundry or personal biases. Sometimes the best thing to do is simply to keep one's mouth shut. It took me over 50 years to learn that lesson - and I do not know if I have truly learned it. Probably not.

    Leave a comment:

  • ngraham
    Senior Member

  • ngraham
    replied
    Originally posted by Awesomeness View Post

    Well, you guys could apologize for ganging up on him and chasing him away. There were literally no reasons to refuse the Sway compatibility patches on KScreen.
    I'm familiar with the interpersonal and technical situation and would not characterize it this way. I have refrained from voicing my perspective publicly out of respect for Roman, because I think he does good work and I don't think anyone benefits when dirty laundry gets aired. But please do understand that every situation which looks simple on the surface is likely more complicated than it seems. There are rarely clear good guys and bad guys.

    Leave a comment:

Working...
X