- Jan 19, 2023
-
-
Jonathan Riddell authored
GIT_SILENT
-
Script Kiddy authored
-
- Jan 18, 2023
-
-
Fushan Wen authored
-
Nicolas Fella authored
This indicates that the applet is automatically loaded based on the presence of a specific DBus interface (e.g. the bluetooth applet is loaded if the bluez DBus interface is present) This isn't clear to the user at all though It provides little useful information to the user and can cause confusion, so let's remove it
-
Script Kiddy authored
-
In the Klipper applet/plasmashell popup, when rendering multiline strings, the final character of each line (except the last) is deleted. So a string like hello there world becomes hell ther world This is due to a bad regex, which this commit fixes.
-
- Jan 17, 2023
-
-
Nicolas Fella authored
We generate a header/cpp pair from the logind interface description For reasons we then replace the generated cpp file with a different one, but keep the original header Qt 6.5 changes some things in qdbusxml2cpp, which breaks this To fix this (and simplify the whole thing) check in the generated header and remove the whole semi-autogeneration mess The logind interface isn't likely to change in a relevant way, so it shouldn't be a problem to maintain
-
Fushan Wen authored
-
Fushan Wen authored
The custom color is specified by "X-KDE-PlasmaImageWallpaper-AccentColor" in the metadata.
-
Marco Martin authored
-
Fushan Wen authored
Use MouseArea::clicked signal to unify code
-
Script Kiddy authored
-
- Jan 16, 2023
-
-
Old behaviour: if the list of items to insert was empty, the model is not cleared. New behaviour: the model is always cleared, even if the list of items to insert is empty.
-
It used to be that when the clipboard history was loaded from disk at Klipper/plasmashell startup, it triggered the `changed` event, and so it also caused the clipboard history to be saved to disk. This is very expensive, since it requires re-encoding every image in the clipboard as a PNG, and is generally just a waste of computation and IO - so let's not do that. As part of fixing this so that we don't save the clipboard history when we load it, the signal setup is changed. Now, rather than destructing and constructing the timer as the user changes the keepContents setting, the timer is created at Klipper construction, and just checks the setting when the History::changed signal is emitted, to see whether to actually activate the timer. This is a much cleaner way of doing it (credit to @davidedmundson for this idea) and means that it's very easy to avoid loading triggering a save: just don't connect the History::changed signal until after we've loaded in the history.
-
This allows us to hash the QImage::constBits directly, rather than re-encoding as a PNG when it gets saved to a QDataStream to be hashed, which is very very slow.
-
Nicolas Fella authored
The spec says it can also carry an X11-style startup ID, so let's do that
-
Marco Martin authored
This tests mostly the calendar view checking that the navigation buttons atually work
-
Script Kiddy authored
-
- Jan 15, 2023
-
-
Bharadwaj Raju authored
| Before | After | | ------ | ------ | | ![Screenshot_20230114_235500](/uploads/bc533d1f8c2f969097437137e3af0b57/Screenshot_20230114_235500.png) | ![image](/uploads/add772f373375d6c071245e878bcea1f/image.png) | cc @teams/vdg
-
Script Kiddy authored
-
- Jan 14, 2023
-
-
Script Kiddy authored
-
Script Kiddy authored
-
Script Kiddy authored
-
- Jan 13, 2023
-
-
David Edmundson authored
We might get screen removal signals and then a re-ordering from the backend or the other way round. In the event that we get the re-order first it's the intention to take this as the single source of truth and remove it from m_availableScreens. In this case we have to notify clients. It's important that this removal is signalled before we process a re-order. BUG:464171
-
The Wayland activation protocol xdg_activation_v1 requires us to send the input serial that triggers the notification as one of the inputs. So far we were always using 0 because it's not trivial to infer which window is the one that triggers the action. This change adds API to specify the calling window so this is not a problem anymore. BUG: 464099
-
Script Kiddy authored
-
Script Kiddy authored
In case of conflict in i18n, keep the version of the branch "ours" To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
-
- Jan 12, 2023
-
-
Fushan Wen authored
Add qml files to Messages.sh
-
Fushan Wen authored
According to ubuntu packaging policies, data dir should not contain arch-dependent binaries.
-
Script Kiddy authored
-
Script Kiddy authored
In case of conflict in i18n, keep the version of the branch "ours" To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
-
- Jan 11, 2023
-
-
Script Kiddy authored
-
Script Kiddy authored
In case of conflict in i18n, keep the version of the branch "ours" To resolve a particular conflict, "git checkout --ours path/to/file.desktop"
-
- Jan 10, 2023
-
-
We can't concatenate sentences like this, it's impossible to properly translate. Instead we have to spell out all 2*10 combinations of scantype and finger BUG: 463976
-
Seems like this bug have been introduced accidentally by 3558eca7 BUG: 450756 FIXED-IN: 5.27
-
Explicitly set pt to pt_PT as a workaround for GNU Gettext and CLDR treating the default dialect of 'pt' differently. See the discussion on: https://mail.kde.org/pipermail/kde-i18n-doc/2023-January/001340.html BUG: 454991 FIXED-IN: 5.27
-
Marco Martin authored
Remove 2 tests that aren't valid anymore as filerenamed is known to be emitted multiple times
-
Script Kiddy authored
-
- Jan 09, 2023
-
-
Kai Uwe Broulik authored
It's a QQC2 `ToolBar` which is a QQC2 `Control` which by default accepts mouse events, cf. QTBUG-89785 This breaks the default action handler in the notification popup, neither showing the correct (pointing hand) cursor, nor reacting to clicks. Only the notification body would.
-
Fushan Wen authored
A test including 3 test cases is added. - New window - Window title is changed - Close window XWindowTasksModel should respond to the 3 events correctly.
-