Commit Graph

19 Commits (6750f02d6f287eb1bf05009b4fd86edf8965fde4)

Author SHA1 Message Date
Michail Vourlakos 60095bba3b fix #96,FEATURE:AllScreens and AllSecondaryScreens
--This is a HUGE FEATURE and so important for multi-screens
users. It is introduced as one single commit because it
reimplements plenty of infrastructure changes and it will
be easier to identify newly introduced bugs.
--Users can now choose for their docks and panels to belong
at various screen groups. The first two screen groups introduced
are AllScreens and AllSecondayScreens. In the future it might
be possible to provide CustomScreensGroup that the user will
be able to define specific screens in which a dock or panel
should be always present.
--Current solution specifies an Original dock or panel and clones/copies
itself automatically to other screens. So docks and panels in other screens
are just real docks and panels that reference themselves to original
docks and panels.
--Clones are destroyed during layout startup and are automaticaly
recreated. It is suggested to export your layouts through the
official Layouts Editor in order to share them because in that case
clones are not included in the new generated layout file. If in any
case you do not this and you share your layout with any previous
versions then your clones will just appear as separate docks and
panels that belong to specific screens.
--Automatic syncing was introduced in order to keep up-to-date
the configuration of Original docks and panels with their referenced
Clones.
--Automatic syncing currently works for all docks and panels settings,
for all normal applets configurations and for all subcontaiments
configuration such as systrays.
--Automatic syncing does not work for applets inside subcontainments
such as Group Plasmoid. In such case it is suggested to configure
your applets inside your Group Plasmoid in the original dock or panel
and afterwards to trigger a recreation for the relevant clones
--Manual recreation of clones is easily possible by just choosing
the dock or panel to be OnPrimary or OnSpecificScreen and rechoosing
afterwards the AllScreensGroup or AllSecondaryScreensGroup
3 years ago
Alexander Lohnau 505379ed04 Use spdx syntax for all files 4 years ago
Michail Vourlakos ae76e82297 viewdata:provide errors/warnings counters 4 years ago
Michail Vourlakos 31b10d9c58 viewsdialog:nice screens visuals for all choices 4 years ago
Michail Vourlakos 7fcfcbc6e5 viewsdialog:concrete implementation for move
--these are the last pieces of code in order for
moving active views between different active layouts
to work properly
4 years ago
Michail Vourlakos c6ee04c8cf data::view split moving flag in two values
--isMoveOrigin/isMoveDestination are flags used
to identify view records during Cut operation
4 years ago
Michail Vourlakos 8b00409d14 viewsdata:add isScheduledForMove flag
--it will help during Cut operations to identify
views that must be moved
4 years ago
Michail Vourlakos 2c8d7134bd simplify Layout::newView calls
--template file is already provided from Data::View
so there is no real reason to expose it one
more time
4 years ago
Michail Vourlakos 4d76005325 viewsdialog:update model data for newly added views 4 years ago
Michail Vourlakos be636de5ce viewsdialog:show view screen edge margin if any 4 years ago
Michail Vourlakos 7630064b36 viewsdialog: view data improvements 4 years ago
Michail Vourlakos 23fe87e736 viewsdialog:add properly new temporary views 4 years ago
Michail Vourlakos 622cc6988c provide debug messages for ViewsTable 4 years ago
Michail Vourlakos a7ac422b31 support running views data from Layouts::Storage 4 years ago
Michail Vourlakos 87ddf1f6d6 update Layout::Storage to Data::View,ViewsTable 4 years ago
Michail Vourlakos 74da7bfb0f add more options in Data::View 4 years ago
Michail Vourlakos 065a3ee9c4 add edge in view data 4 years ago
Michail Vourlakos a48786a5e2 introduce ViewData Origin data 4 years ago
Michail Vourlakos e7eeb4f9fd introduce ViewData and FIRSTSCREENID 4 years ago