IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
--When a layout unloads is setting for its
views a NULLPTR for managedLayout of its docks/panels.
In such case the signals that track the layout
changes for the view are not needed.
--when monitor from an explicit screen was closed there
were cases that docks were moved at another monitor from
the window manager and that was preventing them to be
delete properly. This patch fixes this by considering
as valid explicit screen only the one provided by the
view
BUG: 405687
--onPrimary flag is considered from layout file directly
only for containments that are not already loaded to
latte views
--location flag is accessed directly from containment object
--this is critical because it does not open Latte at
first run. The fix is just to make sure that "latte"
directory will be created in case there isnt already
BUG: 404762
--when Latte crashes the global shortcuts from applets
remain untouched in kglobalshortcutsrc file. That fact
based on the Latte architecture that can alter applet
ids during layout loading can break the global shortcuts
experience by creating multiple global shortcuts records
for the same applet and by disabling some shortcuts because
these shortcuts are already enabled for ghost applets of
the crashed layout. This patch fixes this by removing all
applet global shortcuts during startup. Applet global shortcuts
are already saved in the layout file based on the current
plasma architecture, that fact simplifies things a lot.
BUG: 401184
Summary:
- `timeout = 3000` is a bit short on some computer. Use `timeout = -1` will work for any case.
BUG: 401041
FIXED-IN: v0.8.5
Test Plan: BUG: 401041 is fixed on my computer.
Reviewers: mvourlakos, #latte_dock
Reviewed By: mvourlakos
Tags: #latte_dock, #plasma
Differential Revision: https://phabricator.kde.org/D18258
--moving a task now is not synced immediately to
other docks. Syncing takes place only in the end.
The dock in which the user changed the launchers
order sends a signal to other docks to update
theirs launchers order.
BUG: 401232
FIXED-IN: 0.8.3
--fix wrong placement at multi-screen environment
during startup. freeEdges function was not sufficient for
reconsiderScreen() because there was a chance to
exclude edges that even though they were available
it returned fault results. Such case is when
a view request available edges for specific screen
and the edge of that specific view is also exluded
because that view has not finished its movement
to the new assigned screen.
--fix re-adding an explicit dock when its screen
is activated. A check was missing in order to
confirm that a primary dock is occuping that
edge but we must check also that the primary
screen is the same with the explicit one.
--add/improve debug messages
(cherry picked from commit 0bab34468207b1472c1906c768323f2a9f2b1b12)
BUG: 399456
FIXED-IN: 0.8.2
--dont call costly syncGeometry when drawShadows
externally is called. In such case only updating
shadows/borders is needed.
(cherry picked from commit be7bbfe848fe753239dcd4d9f506a70078212181)
--try to make screens assignment and window geometry
more consistent. There are three variables in a dock
window for its screen and positioning to be accurate,
screen(), m_screenToFollow, m_screenToFollowId
BUG: 399456
FIXED-IN: 0.8.2
(cherry picked from commit f955c6a40c00fb06754223cbdc16ba40e379ca59)
--the new code contains more comments and except
blacklisting all NET::Properties2 signals that are
not accompanied with NET::Properties it also
whitelists specific states for NET::WMState.
This should lower a lot the calculations needed
in order to support the dodge visibility modes.
At the same time apps that are abusing X11 signals
should be ignored totally because the whitelisted
states and NET::Properties are only set by the
user or the window manager.
BUG: 399149
FIXED-IN: 0.8.2
--multi-screen fix for explicit docks. There were
cases that explicit docks during startup were
moving to onprimary screen even though they shouldnt
based on the new multi-screens implementation.
Bug was tracked down at a faulty series of signals
that were overwriting dockView config values
to default values and that was creating the fault.
-- one more fix for multi-screens, a missing return
statement in case an explicit dock is called and its
edge at that specific screen is occuppied by an
onPrimary one.
BUG: 398219
FIXED-IN: 0.8.1
(cherry picked from commit 09fe5e385b4df76afbd342fab61afe6c642aaaf1)
When there was only one latte dock and the last
active window was closed, the dock wasnt showing
afterwards. The dodge logic now has been improved
in order to not lose any window manager signals
that could help indicate when to show/hide a
dodge capable dock
BUG: 398052
FIXED-IN: 0.8.1
(cherry picked from commit 203c740980c594e5e90b4f4b54261561a89c35f0)
--there are cases that the window manager doesnt
return any active window at all. In such cases
we can assume that our docks/panels dont have to
be hidden.
BUG: 398052
FIXED-IN: 0.8.1
(cherry picked from commit 66817695feb76c521b5f7a3dfa1f917b39c4de7b)
when the plasma theme was not supporting shadows then
Latte was double drawing the panel background when
the user has chosen that wanted shadows
BUG: 397980
FIXED-IN: 0.8.1
(cherry picked from commit 87094a6fe7c23de7cb14be1237ccaf1fba28d25e)
--if a dock/panel was containing a systray there
was a chance that the systray was messing the
calculations for adding/removing docks based on
the screen and edges changes
(cherry picked from commit 285a2f87643f9b0387d4364ae6e3a53dceb9fe24)
--Latte will no longer try to be too smart concerning
the multi-screens behavior. At the old implementation
Latte wouldnt let you reach at a state that you dont
have a tasks plasmoid available. Such a case could be
when the user moves a dock from primary to explicit
screen and disables the screen afterwards. That case
should be thought better in the future in order to be
identified and handled properly without making the
code unnecessary complex. Such an example could be by
identifing the case and asking the user for actions.
(cherry picked from commit b2f1f98b5729fabdb00512ff0c90ffcbf44c12fd)
--there are cases that the window geometry isnt consistent
for maximized windows. That was breaking the previous
implementation of dynamic background because of:
https://bugs.kde.org/show_bug.cgi?id=397700
the new implementation is using only the window center in
order to identify the screen in which a window is
present
BUG: 397344
FIXED-IN: 0.8.1
(cherry picked from commit bb8835f156c6cf828d2d8f89d335f813c79dd6a1)
--the background contrast effect should be applied
only when the dock/panel is visually solid otherwise
it may block the transparency settings
BUG: 397431
FIXED-IN: v0.8.1
(cherry picked from commit 78b41eff914e565041598e2777a2eaaa98f74a8f)
--the old code wasnt screen independent for identifying
windows that touch the panel edge. There were cases
that when a window was touching a panel edge at
screen A to faulty identify that is touching
screen B also. The code now is more robust and it
can also handle cases that window is touching two or
more different panels in different screens.
BUG: 397076
FIXED-IN: 0.8.1
(cherry picked from commit 7bceb7e4b752955c0a9be79f57b0485c9271e1ef)
--Improve the series of events in order for CopyDock
to work better in multi-screen environments. Copy Dock
should create the same dock in the same free edge at
different explicit screen when that edge is already
occupied in the origin screen
BUG: 397081
FIXED-IN: 0.8.1
(cherry picked from commit 30c90d2a419c8c367a7a2f3887b7a11bd4f8de6b)
--after v0.8 release many issues with multi-architecture
were identified. An alternative approach was needed
in order for Latte to get a more user-predictable state.
In new approach:
--onPrimary docks have always higher value
and should be shown, this is also like how plasma is
moving its panels.
--explicit docks are removed if their edge in their screen
is occupied by an onPrimary dock
--be stupid smart in order to check if docks contain
tasks and try to not remove them based on screen-changes
is removed! Over-Complicated code that doesnt help
in maintainability...
one of the issues was reported at following bug report...
BUG: 396806
FIXED-IN: 0.8.1
Summary:
In Latte global shortcuts is missing one record
for New Instance of ninth record
BUG: 396751
FIXED-IN: 0.8.1
Subscribers: plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D14273
--v0.8 introduced unified global shortcuts for all
cases, that means that applets are also taken into
account for Latte activation/new instance global
shortcuts. A new parameter is introduced with
the patch at Latte global settings file called
"unifiedGlobalShortcuts", the user can set that
parameter to false before Latte startup in order
to use only global shortcuts relevant to the
Latte plasmoid.
--when changing Single mode to Multiple mode the latest
changes from user didnt get into because the kde cache
from KFileConfigPtr hadnt been updated yet. This
patch fixes this by using a temp file that contains
the layout in question.
