Related: apps/orage#32, xfce4-dev-tools!101

Ian authored 10 months ago and Gaël Bonithon committed 10 months ago

Helps: #194

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

214 translated messages, 1 untranslated message.

Transifex (https://explore.transifex.com/xfce/).

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

213 translated messages, 2 untranslated messages.

Transifex (https://explore.transifex.com/xfce/).

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

Juan I Carrano authored 1 year ago and Gaël Bonithon committed 1 year ago

Pressing the XF86XK_KbdLightOnOff (kbdillumtoggle) will cycle through
the available brightness levels (it will increase brightness up to the
maximum and then go back to minimum).

If the keyboard has only two states, this behaves as a simple toggle.

The reason for cycling is that it is unlikely that a laptop will have
all three buttons for brightness up, down and toggle. If the machine
has only a toggle button and more than one brightness level, a simple
on/off (or min/max) toggle will not allow to use the intermediate
levels.

Closes: #222

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

If the xfconf property does not exist at all, it won't touch the
switch's state.  Since xfpm defaults to TRUE, we should set the switch
active by default in the UI description.

Closes #33

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

If the setting was set to never before this change, this will have the
effect of setting it to 14, since this value was used as a reference for
disabling system sleep. Unfortunately, this is unavoidable and it is not
possible to implement backward compatibility, since 14 is now also a
possible value. Users will therefore have to manually set the value to 0
to disable system sleep after this change.

It's an inconvenience, but this behavior really deserved to be fixed.

Fixes: #3

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

199 translated messages, 16 untranslated messages.

Transifex (https://explore.transifex.com/xfce/).

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

It's too early to determine the windowing system at this stage, as we
haven't yet called gtk_init(). And if we do call it, we can no longer
daemonize below, as was mentioned in a comment about
gtk_get_option_group(). So the simplest thing to do is to always add
this option group (provided you're compiling with X11 support), which
activates very little code in libxfce4ui and nothing specific to X11.

Fixes: 15180f36

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).

215 translated messages.

Transifex (https://explore.transifex.com/xfce/).