TODO: store the descriptions in KKeyboardLayout such that when adding items
to, say, QComboBox the items will be pre-sorted
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
lots of changes with this commit - on the plasma applet side:
+ the applet now handles mouse wheel events
* the applet itself sets its global global shortcut key
+ the applet itself has configuration interface for the text and flag options
* ported to the new KKeyboardLayout class
- no per-window or per-application keyboard layout
on the overall keyboard configuration:
* no KDED module required
+ keyboard layout descriptions (model, layout, variant, etc.) are actually translated
- no keyboard configuration will be shown when a keyboard is plugged-in (see bellow)
- keyboard layout options are not configurable, not via GUI interface anyway
the hotplug plasma data engine, device notifications and solid actions
have to be either reimplemented or extended to handle more device types
(currently the above mentioned handle only removable devices by default
such as cameras, not input devices such as keyboard)
overall - from reimplemented one thing to another and the keyboard
configuration is not done yet (adding and editing keyboard layout not
implemented yet) but in a working state
on a side note the changes here affect kvkbd as it uses D-Bus interface
for keyboard layout change that is no more and has to be ported or (most
likely) replaced with a handler for QEvent::RequestSoftwareInputPanel
event that shows a keyboard on demand
there is also the double-keyboard layout applet thing - applet for the
keyboard layout could be added and the daemon (KDED module) was showing
its own keyboard layout indicator automatically (by default)
the X11 keyboard bell options are next to useless btw - there is
KNotification::beep() for such things so the X11 bell options are
simply dropped
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
now with separate options for screen and sleep power management
suppression as well as being able to select which battery to show
information (including icon) for in the tray:
https://ibb.co/DDC01rh
the battery icon is questionably bigger than it should be, have to test
it with battery that is recognizable still (PS3 controller battery
provides only capacity and status info)
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
also open the program bug report address, unless it is official Katana
application in which case the default bug report URL will be opened
(defined as KDE_BUG_REPORT_URL)
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
because KUrl passes the URL as-is when it is constructed from string (char
array, QString, etc.) query items (intentionally) are not splitted, fixes
restoration of task manager launchers
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
if only there was a way to tell browsers:
Hey, browser! Don't decode the URL - you don't know where it points to!
for reference:
https://ibb.co/cyhwppK
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
because the files are marked as output for custom target and custom
command the build system deleted them after reconfigure..
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
note that it is independant of X11 multiscreen, as the comment in
KWin::Workspace::isOnCurrentHead() claims
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
the UID can be obtained via other means and KDE_SESSION_UID is no longer
required by kded, see the following commit in kdelibs repo:
e482da906734dcd5434fc322eac262c775125825
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
grabbing the pointer does not play well with the kwin mouse interception
feature, notably for the presentwindows effect
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
plasma-desktop wallpaper does not affect other applications, not during
startup and not after startup is done
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
kded no longer requires it during early startup, see the following
commit in the kdelibs repo:
e482da906734dcd5434fc322eac262c775125825
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
see 387bdaa93fd6adb0cd8a930454e3be578fa5fdc0 in the kdelibs repo, how a
link will be opened depends on a few things now - the MIME type and what
method is used for opening the URL. if KRun is used the MIME type will
be detetermined and the prefered service for it will be launched, if
KToolInvocation is used first the preferred service for "text/html" will
be attempted with fallback to kde-open and xdg-open which solidifies the
behaviour of "mimetype-determination-in-calling-application" (see
kdelibs/kdecore/sycoca/kprotocolinfo.cpp)
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
