some important paths such as those for the plugins were missing before
resulting in configuration fails after 4253ed73
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
this ensures that, for an example, when kdelibs locales path is
changed via CMake variable override that locales will be installed
in the same path that was specified
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
it is needed in Okular and in KNotify I think so with the overload method
the possibility for MPV API break to affect those application will be
reduced, KAbstractPlayer is ment to be abstraction after all
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
it is obviously the wrong approach to report applications crashes
as is noted in the comment in kdebug. since it is only for
KApplications, which provide D-Bus interface, it can be handled
differently with a separate daemon that monitors for wrong
behavior but that is not needed really since DrKonqi does a fine
job at providing feedback when such even occurs
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
the change is questionable, the application may have different use case
for it but with this change it displays errors and currently played path
title which is kinda usefull if there is no window manager at all
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
basicly once the hack is used m_parent becomes valid widget, to avoid using
it the second time fullscreen is requested just set it to NULL thus making
it invalid and the hack will be used again
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
the point is to reduce the horisontal lenght of the widget while simulating
a gap between the text (label) and the other widgets. also even when the
dialog is resised, the text should always stay on top of the widget not
moved to the center of the dialog
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
there was only one now backend (INI) and changing it on the fly
(as was supported before) can cause serious issues with
applications misbihaving and such
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
without extra path property check it can be emited twice (or even more?)
because MPV will try to use SSL and fallback to non-secure connection when
that is not possible and emit the event after load which, aside from being
innacurate for our use cases, causes unnecessary widgets actions.
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
it has too many side effects that will complicate things more then it is
worth it to save a few MB of RAM per-application until load
Signed-off-by: Ivailo Monev <xakepa10@gmail.com>
