Can’t help but I just did this myself. Was a fairly fresh install so I didn’t lose anything other than have to reconfigure some stuff and install some things.
Buuuuut
What happened dto me was something crashed during the update and my computer went to a black screen. So I just left it for a bit to hopefully finish even without the display. Turned the computer off and my nvme was just gone. Ended up having to get a new one.
Nope. I think the drive just died at a bad time honestly. I’ve had issues with it in the passed and the computer itself came from an e-scrap pile because the water pump for the CPU cooler was dead. Has worked great since swapping that out until the nvme died. Even after installing the new nvme and reinstalling EOS I couldnt see the old nvme.
Its been a while sinse I’ve used plasma, I had the same issue but I was using nvidia at the time and nvidia has a tool to set refresh rate, screen size and a lot of other things, gsync/freesync being one of them. Now most monitors do have if gsync/freesync enabled an option to turn it off. but before you do that if you have other display port/ HDMI cables around then switching though them would be advantageous as youll avoid screen tearing
“fullscreen” cannot be used as a condition in windows rules AFAIK, but you can achieve this with a simple kwin script (the syntax is very easy, nothing to be scared with). You can find on the KDE website a tutorial and the whole API set.
Let me show you: We are going to add an event listener listening to any client going fullscreen (or de-fullscreening), and then we will apply the “keep below” property to the fullscreen ones.
you first need to add a rule to listen to clients changing fullscreen status: (references)
This will call the function fullscreenChanged each time a new client changes its fullscreen status, passing to the function the client. ( I don’t know why but workspace.clientFullScreenSet does not work, it would have been better, but whatever)
We need now to write the fullscreenChanged function. It should change the KeepBelow status, evaluating if the client has been fullscreened or de-fullscreened:
you can follow the instruction on the tutorial on how to install it. Hope this helps!
(I haven’t tested it much, in case of any problem feel free to ask!)
I noticed this in video games rather than on-screen text scrolling. Some of them had a weapon selection, but instead had mouse-wheel-down “decrease” the weapon slot, and mouse-wheel-up “increase” it. However, the game also used the mouse wheel for other things, thus changing it to my preference had some unexpected side effect.
In any case, mouse-wheel to scroll view works because of the mouse-pointer paradigm. Move both mouse-wheel and mouse in the same direction, and the pointer is further along the content. Move them in opposite directions, and the pointer tends to hold position relative to content.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.