Does a "cut out" around the "running" badge for contrast.

Does a "cut out" around the badge for contrast.

Consensus is: Nobody will invest any significant time into this, so remove it from System Settings and make it a standalone app instead.

https://gitlab.freedesktop.org/xdg/shared-mime-info/-/merge_requests/156

+1 referencing a KCM in the metadata for the few that need it is surely better than baking a widgets dependency into the API

Media Session API gained "video conferencing actions, could be useful to expose those actions through p-b-i somehow: https://web.dev/media-session/#video-conferencing-actions

There's an effort for a cross platform wake lock in Qt: https://bugreports.qt.io/browse/QTBUG-89477

either KActivitiesStats can do file watching

Can we make sure KActivitiesStats or whatever recent docs thing is aware of the new location used y KRecentFileMenu. I believe @meven worked in that area (e.g. for GTK file dialog feeding into that, too).

In doubt we could make a dummy binary that is DBus-activated that then calls loadPlugin. Dbus doesn't care who registers the service, doesn't need to be the process it spawned.

There's now a QNetworkInformation class [1]. Currently it only does "is online", no captive portal support and no metered detection. It's a start at least.

I can only re-iterate what I said before:

What about KPluralHandlingSpinBox? It's basically just a QLineEdit with ki18n.

The menu is already massive as it is. On my laptop it fills the entire screen height and a good portion of its width, I'd rather see it compacted and streamlined again than put even more items on the top level.

Double-click is what everyone is used to from other desktop platforms

I think having an "interrupted" state (or something along the lines) would be useful which is set when the job is waiting for user input (e.g. whether to overwrite or to skip something), so that this can be indicated to the user. E.g. windows turns interrupted jobs yellow in task bar from what I recall.

A non-representative poll in the hallway track last night suggested we should default to the right Ctrl key for push to talk.

Should we go with this now? I haven't seen it crash on me since I fixed the checkIndex thing

I now have runner queries never "finish". I type "plasmashell", get the results I expect, and the busy indicator keeps spinning forever.

We have image/video/audio now, text selection I might add later but maybe not soo useful after alll

I'd prefer some dimmed label next to the app name but with the radio button and manual size calculations all over the place now, this is difficult

Let's revisit that should it ever come up again :)

@davidre said something about that we don't show small thumbnails anymore anyway or something

I've got a jobviewv2 thing in the works which is qvariantmap-based so it can easily queue any changes and send them out once registered. I think jobviewv1 should just stay as is and be phased out eventually, cf. T12574

I've got a jobviewv2 thing in the works which is qvariantmap-based so it can easily queue any changes and send them out once registered. I think jobviewv1 should just stay as is and be phased out eventually, cf. T12574

I've noticed I accidentally removed compiling a few things, that also depend on KIO, so maybe not as lean as I hoped

In T13156#230900, @ndavis wrote:

Is there a way to set the default panel based on info about the user's screen?