Sentau

joined 5 months ago
[–] Sentau@discuss.tchncs.de 1 points 1 day ago* (last edited 1 day ago)

Currently, gnome has moved away from eye of Gnome to Image Viewer/Loupe. The website doesn't have the dependencies though I don't think you should need the gnome-desktop package. Perhaps you can look into it. Just be aware that the app is pretty barebones for now.

Edit - Alternatively, you could look into gwenview which is normally shipped in kde. That will have the advantage of shipping with a lot more editing options and since it is a more mature(I think is the right word) project, I expect it to have better support for esoteric file formats.

[–] Sentau@discuss.tchncs.de 1 points 3 days ago (1 children)

Well fitts law doesnt mention anything about asymmetrical spacing anywhere. Infact going by fitts law, the new gnome design is great because the hitboxes are pretty large

[–] Sentau@discuss.tchncs.de 1 points 3 days ago (3 children)

Can you share any study for this. If this is true, it is fascinating and worth looking into in more depth

[–] Sentau@discuss.tchncs.de 10 points 4 days ago* (last edited 4 days ago) (5 children)

That same logic could be applied for the save and discard button. Should there be a bigger gap between them lest somebody misclick and discard things instead of saving them¿? Atleast in the case where they accidentally click cancel instead of discard, they are not losing any data.

Hell if this really about data safety, discard/don't save should be the isolated button because it is the only destructive option

[–] Sentau@discuss.tchncs.de 15 points 4 days ago* (last edited 4 days ago) (7 children)

Here's the thing: Apple's design you'll find that they carefully included an extra margin between the "Don't Save" and "Cancel" buttons. This avoid accidental clicks on the wrong button so that people don't lose their work when they just want to click "Cancel".

And gnome has those dialogs in a different colour to achieve easily noticable differentiation between the two options

[–] Sentau@discuss.tchncs.de 1 points 2 weeks ago* (last edited 2 weeks ago)

That was an incredibly poised and informative response by Carlos. Thanks for linking it. Cheers

[–] Sentau@discuss.tchncs.de 1 points 2 weeks ago (2 children)

Oh ok. Are these changes tailored towards making touchscreen usage better¿?

[–] Sentau@discuss.tchncs.de 11 points 2 weeks ago* (last edited 2 weeks ago) (4 children)

Yeah. Scrolling(amount of scroll per turn of the scroll wheel/swipe on touchpad) has been intentionally slowed down. Another issue is when you scroll fast, the scrolling is stuttery because papers tries to render on the fly when scrolling. There is an open issue to discuss whether this should be the behaviour or not.

But don't worry too much. It was much slower a month ago and yet progress is being made at a great pace and hence I expect it to get better in the near future. Pablo Correa Gomez(the lead dev of Papers) is doing some great work.

[–] Sentau@discuss.tchncs.de 20 points 2 weeks ago* (last edited 2 weeks ago)

Well for Firefox, the one getting updated is the native rpm version which is part of the standard Silverblue install while the one already updated is the flatpak version. The native version is just called 'Firefox' while the one from flatpak is called 'Firefox Web Browser' if I remember correctly. I have no idea why signal is showing up there. Maybe it is a bug.

Also next time a system update is shown in GNOME software, check using rpm-ostree status to see if any updated image is staged. If yes, then you don't have to bother with gnome software - when you shutdown or reboot, the update will automatically be applied.

[–] Sentau@discuss.tchncs.de 8 points 3 weeks ago

I think evince will be eventually dropped by GNOME but there is time for that. While papers is porting things to GTK4 and adding some great features, it still has a long way to go in performance and optimisation. Currently it is more than twice as slow to open a pdf when compared to evince. Also scrolling performance is not optimised as it will stop mid scroll for things to render. Well it is only a new project so hopefully all this will be fixed. I am still using papers so that I can report any bugs that I run into

[–] Sentau@discuss.tchncs.de 2 points 1 month ago

I love this comment because it explains the keywords in the command. Hats off to you.

[–] Sentau@discuss.tchncs.de 2 points 1 month ago* (last edited 1 month ago) (1 children)

Hmm. Maybe gnome is not correctly using hardware acceleration in your machine¿? In my experience, gnome is perhaps the smoothest DE though it is heavier in resource usage than XFCE, MATE, etc. It does stutter and drop frames when the system is seeing very heavy resource usage.

Edit : when I am using the powersaver settings given by power-profiles-daemon, gnome does stutter a little. This corresponds to amd-pstate being active with the scaling governor set to powersave and the energy vs performance hint set to save power.

 

Words cannot express just how much I love the new setting to quickly toggle between light and dark mode. I am very very grateful. Thank you @aeharding@lemmy.world, this is a wonderful app.

22
DRM error in F1TV (discuss.tchncs.de)
submitted 4 months ago* (last edited 4 months ago) by Sentau@discuss.tchncs.de to c/formula1@lemmy.world
 

Since there is no F1TV community, I am posting here. I am trying to watch the pre season test on my phone running but am running into the error in the picture. My phone is running lineageOS 20. Is this a widevine certification issue¿? Is there anyway to resolve this¿?

Edit : Further phone details - Motorola G60. F1TV app used to work normally with the stock rom(at least it did last year)

view more: next ›