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 removeView is called the relevant containment
should be first removed from containments relevant
layout list in order to not be reenabled through
syncLatteViewsToScreens
--moving views between different active layouts can be
tricky because three different scenario should be handled:
--- onscreen_view -> onscreen_view in different active layouts
--- onscreen_view -> offscreen_view in different active layouts
--- offscreen_view -> onscreen_view in different active layouts
--last week commit about beautiful slide in/out through
kwin infrastructure broke the wayland placement for
docks and panels. This commit fixes the issue
and at the same time provide beautifule slide in/outs
for docks panels during their creation and removal.
--update Layout::removeView implementation in order
to call containment "remove" function directly.
That approach works more reliable than the previous
one and we are that in the end no orphaned containment
config data will be present in the layout file.
--it is going to be used in order for
Duplicate/Cut/Copy functionality to be supported
properly. Its main purpose is to accept a
layout and a containment_id and based on
that to provide a stored view temp file
which is going to be used as a template
for any future addition.
--we now accept Explicit Views in the same screen edge
with OnPrimary Views At ALL CASES and we do not remove
them until the Screens properties have created a deprecated
valid Screens Views Map
--add layout slot to update lastUsedActivity
when runningActivities where changed in order
for layout::applyActivities() to provide valid
activities list even when an activity is
first starting.
--when the user requests a specific layout in Multiple
Layout mode the new approach is the following. If
the layout has assigned activities this is respected
but if its activities are empty that layout is assigned
only on the current activity and any other layouts assigned
explicitly to that activity are released
--the controller does not need to host its own
CentralLayouts any more. It retrieves original
data for Synchronizer, updates layouts accordingly
and sends back to Synchronizer all the updated
layouts data
--Move in a simpler layouts approach.
--Single Layout mode loads ONLY ONE Layout for ALL Activities
--Multiple Layouts mode loads any combination of Layouts based
on the following settings:
-- OnAllActivities
-- ForFreeActivities
-- SpecificActivities
