the color 'universal_overlay' can be used as backgrounds for
semi-transparent overlays.
the color guarantees enough contrast to white/light things drawn on it,
while still letting the background shine through.
the color is the same for both, dark and lite theme
as it is also used to draw on customized backgrounds
(where we can have any background anyway)
before, the shaped formed with this color are not visible
on black background, this is fixed by this commit,
making the color even more universal.
this is an improvement for the image-editor buttons
as well as for the info-messages on arbitrary backgrounds.
when server-deletion is enabled,
always show a hint about the impact below the option.
the hint is a summary of the conformation-dialog
so that the user is more aware of the impact
if enabling was some time ago
or the option was even enabled by the provider-db.
this pr changes the wording,
not relativize things, underlining the worse impact.
i avoided adding "maybe" or "potentially" here,
even if that would be more accurate.
moreover, the pr adds some red color and emojicons.
when forwarding to "saved messages",
the ui goes back to the chat and the position in the original chat
and shows a short "saved" hint.
this saves at least one tap,
and makes saving multiple messages easier
as you stay in context.
btw, this is also how telegram handles things
and makes the saving as easy to use as starring eg. in whatsapp.
forwarding messasges to other chats is not changed.
the warning about outdated apps
was pretty unreliable in the past -
because of too short timings
and also because of the "installation date"
and the fact that an "installer" was used, is not always reliable.
also, the "installer date" could be wrong -
if the installation was done when the clock was altered badly.
as we cannot rely on the things the system provides here,
we move the whole thing to the core at
https://github.com/deltachat/deltachat-core-rust/pull/1901
which has also the advantage that this is done for all uis then.
errors that should be shown to the user
come from DC_EVENT_CONFIGURE_PROGRESS(data1=0) as data2 now;
there is no need to show the captured error any longer
(which was unreliable and hard to handle from core site).
there is some capturing-code left as needed for other parts,
but it is not used for configuration anymore.
while it is more straight-forward to let the system ask the user directly -
as we do for most other permissions -
this is probably not favorable for requesting ignore-battery-optimization:
- other permissions requests are preceded by a clear user intention -
tap on the camera, record voice etc.
so it is clear to the user why a permission is needed.
this is not true at the moment after installation
(maybe the moment can be improved, btw)
- different systems have completely different text,
partly focusing on "battery drain" - it is not clear to the user
what would be the advantage of that
- some guidelines say, user interaction is needed before querying permission.
there is room for interpretation, of couse,
however, adding a rational with a "continue" button
seems to fit better to these guidelines.
removing unneeded strings makes work of translators easier
and also, in sum, saves some amount of data.
checked by ./tools/grep-string.sh that the strings are not in use by other os.
as checking is some work, i only targeted low hanging fruits,
there may be some more strings unused.
B. Petersen