The hands in the fourth pane…

I am both at the same time.

I took only until recently (two years ago) to watch Breaking Bad and found it like, okay, I guess. I just didn’t get interested enough to watch more than the first episodes.

Usually I am the sort of person who watches things to the end and hypes about popular things like Deltarune.

The seeming lack of month ordering doesn’t feel like it would be intentional after all.

That is a decent way of finding out whether the person is a native English speaker, actually.

This rarely happens to non-native speakers.

I’d do that without a sigh :p

Relevant:

• https://discuss.kde.org/t/kde-in-the-ansible-community-collection/1905

• https://discuss.kde.org/t/plasma-and-ansible-on-enterprise-thin-clients-changing-default-plasma-settings/18142

You’ll probably need to send a ticket to sysadmin to have that issue sorted out.

In that section, if you click the button to configure the Mouse Mark effect, you can see the shortcuts for clearing Mouse Mark:

• Clear last mouse mark: Super + Shift + F12
• Clear all mouse marks: Super + Shift + F11

A small correction:

For example, there are Kirigami bindings for Python you can use to do a desktop/mobile app.

Kirigami is QML all the way, it doesn’t need bindings since you’d be writing in QML either way. The Python part is about the actual business logic. :)

I’d be curious to see a blog post in the future mentioning the challenges you might have faced making the dock work on Wayland, and what was needed for that.

When you search using the Starred filter, usually you get the main project at the top since that’s the one with the most stars.

I added a KRunner web shortcut for this that automatically searches using that filter: https://rabbitictranslator.com/kfluff-web-shortcuts/

Looks like an old bug with kscreen that could cause two screens to merge together and would be worked around exactly the same way you did. I used to have that whenever a blackout happened, but only with Plasma 5, and often on X11.

Everything. It doesn’t accurately describe the issue (animation stutter when using an HDD or during heavy I/O) and it doesn’t mention the solution (put the cache folder in tmpfs), plus it obviously follows the traditional sensationalist tone used in clickbait.

The point is to be deliberately vague to bait people into watching it.

We’re always open to doc contributions. Interested in any particular areas? 🐰

What’s the best or recommended way to test out Plasma 6 RC2?

See also: https://community.kde.org/Plasma/Plasma_6#How_to_use/test_it

without the need of the moc

I got a bit of a mind freeze reading that sentence since my first thought was “why would someone deliberately give up on Qt’s reflection system” but only then realized they’re still using QMetaObject (the thing that actually enables reflection and signals and slots), just building it with something else.

This was shared recently by a friend I follow: https://mastodon.social/@silvereagle/111484800732591545

Direct link: https://www.sofurry.com/forum/view/thread?id=58457&page=100000

That link has a few mentions of podcasts:

• 24/7 Chill Furry Lo-fi Radio https://www.youtube.com/@AquariusCrystalwave/streams
• Furry Refuge (Old streams) https://www.youtube.com/@furryrefuge3969/streams
• Catnip Radio https://www.mixcloud.com/CatnipRadio/stream/
• Furry Rave Crew https://www.mixcloud.com/FURRYRAVECREW/

Also, you should only use Layout attached properties when the object you’re using it on is a child of a Layout, for example:

ApplicationWindow {
    ColumnLayout {
        anchors.fill: parent // Not a child of a layout, so you use anchors
        Controls.Button {
            Layout.fillWidth: true // It's a child of a layout, so you use Layout.fillWidth
        }
    }
}

So what you want to do is put a Kirigami.SearchField inside the global toolbar created by the Kirigami.Page. It’s not a header.

In the first case you’re putting it inside the page, and because it’s a direct child of a Kirigami.Page, it is automatically laid out for you, which is fine, but not what you want.

In the second case you’re putting it in the header of the ApplicationWindow, but you actually want to put in the global toolbar of the page, so it’s not what you want.

In the third case you’re just putting a SearchField before the initialPage, so it’s loaded on the same level as the page, it’s not what you want.

You can put it in the header property of the Kirigami.Page, but the header area of the page doesn’t include the global toolbar, so they just happen to be close together by chance.

The way I’d have expected to do that would be to override the globalToolBarItem of the Kirigami.Page, but it’s read only, so I don’t really know how to help you with that. You should ask in the Kirigami Matrix room or in the Discuss forum.