for proxy settings there can be KCM that sets klauncher variables for
proxy preferences, has yet to be decided tho
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
screen inhibition based on monitor name and lid button presence sounds like
someone wanted X11 DPMS (which is automatic nowdays) on his laptop to me
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
KDialog::marginHint() is kinda deprecated right now, the margin depends on
the style hints anyway which KDialog::marginHint() is a shortcut for
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
can implement condition for when device changes occurs too but I have no
plans to use it for something, not yet that is. the remove condition can
(and probably will be) used to start kvkbd when there is no keyboard
plugged in altough that will require program to check when to do that
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
I've tested only the grp:alt_space_toggle option, don't even want to know
what kind of issues the other option will cause. feel free to file issues
to X11 tho
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
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>
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>
so that events can be processed and the modal dialog about accepting the
changes does not block the event queue
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
no idea what "artsd" is but figuring out in what format standard sounds are
is easy - just look into /usr/share/sounds. also, the sound files shipped
by Katana are in OGG format
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
the idea being to not write anything into the Katie config and possibly
even drop support for overriding Katie settings from config.
on a side note font and palette settings are wrapped via classes
(KGlobalSettings and KColorScheme) and hard-wired to configs rather than
being a runtime thing (e.g. getting the font to use for menus via
QApplication::font("QMenu") instead of KGlobalSettings::menuFont()) so lots
to do on that, as for how it will benefit Katana and Katie - less config
parsing possibly, QPalette objects are shared data for example
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
otherwise it looks as if it is currency or something like that (e.g.
"1,920x1,080") and does not match the number that is shown in the combo box
with available resolutions
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
