| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Exposed fontSize as a separate alias so other
Label components in the system are not affected.
This should be a temp solution since we will bring QCC2
and should solve issues like this on system level.
Change-Id: I037a1f7bb42e4f444f2007b97efe2f061bb36994
Tas-number: AUTOSUITE-48
Reviewed-by: Alistair Adams <alistair.adams@qt.io>
|
|
|
|
|
|
|
|
| |
Displays all windows in a grid and closes the applications on
a press on the X
Change-Id: Ie88e2a6ad1225cf710a30fe72ea2d0b667b26e95
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
|
|
|
|
| |
The additionalConfiguration property will be removed
from ApplicationManager and systemProperties will be
used instead.
Change-Id: Id34ee6033d58f9b799791db71a95926fca3ec99a
Reviewed-by: Bernd Weimer <bernd.weimer@pelagicore.com>
|
|
|
|
|
| |
Change-Id: If13fce55ad9a89e1ed2561a68e03a390e354ba6d
Reviewed-by: Dominik Holland <dominik.holland@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
| |
It wasn't connected before, now changes are propagated both ways,
and even the list of available airflow configurations comes from
the backend.
Change-Id: I69e61fd795014c2e3f0f98832b828a302ace5d34
Reviewed-by: Jaroslaw Kubik <jarek@froglogic.com>
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
Reviewed-by: Dominik Holland <dominik.holland@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In current implementation the property bindings between QtIvi backend
properties and GUI object properties are used for two-way communication.
In case GUI requests a change, the requested GUI object property is assigned
with a new value. This operation removes property binding to the QtIvi
backend. Additional code in onXXXChanged: handler must be written explicitly
to propagate the change to the backend and recreate the binding afterwards.
This scheme is difficult to maintain and test.
In this modification a second channel is introduced - the property bindings
take care of propagation of updates from backend to GUI, and functions are
used by GUI in order to request backend changes. GUI itself does not update
it's own internal variables on user actions, and instead relies on property
bindings to follow the change in backend - this approach makes the code
simpler, avoids binding recreation, and handles well cases where backend
properties changes value to a different than assigned to it - backend can
react to property assignments in non-trivial ways.
Change-Id: I55423fe806d1db9d099c7983676dd1afeb1b5b69
Reviewed-by: Andreas Hartmetz <andreas.hartmetz@kdab.com>
Reviewed-by: Harri Porten <porten@froglogic.com>
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
|
|
|
|
| |
Instead of trusting the visible property, we now set a state to
ensure that we know that the window is already handled
Change-Id: Ie3b205b9c458789fed142dc9cb9ed3b58c9db8b9
Reviewed-by: Dominik Holland <dominik.holland@pelagicore.com>
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
| |
Using the scaling was causing image not to look
natural and could cover other parts of the cluster.
Updated dial animation parameters. The old ones were
slow.
Change-Id: I6d7c4f6f7577b1700f511a110d89ae75898defa7
Reviewed-by: Juergen Bocklage-Ryannel <juergen.bocklage-ryannel@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
| |
* Removed unused elements and properties. They were
project specific
* Exposed properties to apps in order to manipulate looks
for the simulation
* Updated right dial layout
Change-Id: I3eae3f50d2871e218370d6f1ea685c6998625fe7
Reviewed-by: Dominik Holland <dominik.holland@pelagicore.com>
|
|
|
|
|
|
|
| |
This part was lost during a rebase.
Change-Id: Ia148b5f78cc4bf17dfb3da677fbec263fc999a00
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
| |
- The value is [...].seatHeater.value - with ".value"
- Propagate changes from UI to backend and vice versa. Previously,
if it had worked (see above), the backend -> UI direction
would've been broken by the first UI -> backend assignment.
Change-Id: I5f88ed6926f59acda94bd47d99c51c629135b027
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, two things did not work:
- Changing by more than one level by directly tapping on the
desired level. This was apparently intended to work but
didn't, from looking at the code.
- Changing by more than one level from the backend
In both cases, the NumberAnimation on the view's index which was
aliased to the ventilation level caused a changed signal for
every step change, which, because it was the most recent change,
became *the* change and caused the final value to fall short of
the actual target value.
After the core fix, a similar fix to the previous one is needed
to make the backend to UI propagation work at all again. But
then it works right.
Change-Id: I31d7f247203cf25b17d06d0eb4edc7af81af4334
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
|
|
| |
That direction did not work, only UI to backend.
Change-Id: Ifb4d53f5c8992fb88ad4ae62a89c4de0da6f9562
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
| |
Change-Id: I503bc495a23c9bea2f5bc740d6976732d0caed77
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
| |
Change-Id: Idb8544151425c859dbccd1889e41123ef7ab95e4
Reviewed-by: Alistair Adams <alistair.adams@qt.io>
|
|
|
|
|
| |
Change-Id: I68414160bf3582a1c4f67d0892458bb55de5c291
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All WaylandSurfaces regardless of whether they are accepted or not
need to part of the visual QtQuick item tree, otherwise they will block
the event loop of the client.
This commit introduces a unhandledSurfaceReceived signal, which is
handled by the LaunchController and reparents the surface into the
visual QtQuick item tree.
Change-Id: I80f3de7ef9183ecdade7c4683e4087ea3f5e12fa
Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
|
|
|
|
|
|
|
| |
This can lead to a white background in the app launch transition
Change-Id: I7b62e778240fcf6a2bb69c56678b6e98648ba57e
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of having our own detection in the AutoConfig.qml we now pass
the "showClusterIfPossible" to the config and decide what's needed
based on this value.
Otherwise we might end up in a situation where we show an instrument
cluster, but the Compositor doesn't know about it and doesn't accept
the windows
Change-Id: I7929f8a95f3d6462b63d856aaa51c93a87881786
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
|
|
|
| |
* Updated API to launch system monitor
* Always enable dial animation
Change-Id: I309804188c84ba0f9f3b2843f0b5b27cc81eb23f
Reviewed-by: Dominik Holland <dominik.holland@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It's now possible to start multiple applications and stack the windows
on each other. If a window is currently visible and an second application
was started, the new window will be stacked on top. The back button
will reveal the previous window again.
If an window in the stack which is not the current window is closed.
The window is removed from the stack without animations
Change-Id: I0d2b0010ffe4ec07bb075d53c5ba524b52d55a7c
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Always maintain a list of all windows accepted by the system-ui
and their type. Depending on the type we know what needs to be
done in case the application is closed or stopped.
This is needed to properly release the surfaces of all windows
we accepted. IVI windows which are not minimized need to poped
from the stack first and a closing animation be played. All other
surfaces can be released once the surfaces are lost.
Change-Id: Ie8ede8c2b14b288d1a182d7c32095c2c4c90b845
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
|
|
|
|
| |
Vehicle service should be part of the system UI
and not available to an app. It is renamed and moved
to system models.
Change-Id: Ic00c4cc1835ab4ec7a134fc60fd6dbacb63944cf
Reviewed-by: Dominik Holland <dominik.holland@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
| |
Previously we maintained an own list of applications which should be
auto started and minimized.
Now we use appman's preload property in info.yaml to identify the
apps which are autostarted and should be started minimized
Change-Id: If0be0732de25da73ac6fce02dee2ffbd843bac47
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When starting an application in the minimized state we still need to
accept the window, but reparent it to a dummy item instead of pushing it
into the window stack. This is achieved by extending the
applicationSurfaceReady signal with a isMinimized property.
Also use the new isClosing property of the application manager to
identify closing windows. This is needed to make sure we only raise
windows which are in a usable state.
Change-Id: I0a5d544576859024b3f33e0814e72707bc692621
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
Reviewed-by: Erik Botö <erik.boto@pelagicore.com>
|
|
|
|
|
|
|
| |
A very basic sample of a radio application
Change-Id: I7d26482726791356f558b0182b99df37af9d465b
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
|
|
|
|
| |
Moved the CarDemo component in the My Car page to a module. This makes it
easier to replace it with a different component, such as the Qt3D-based
component (in a separate repository).
Change-Id: I91147a1aa7483b9045feee9964cea4528c348836
Reviewed-by: Dominik Holland <dominik.holland@pelagicore.com>
|
|
|
|
|
|
| |
Change-Id: Icb36cf995d422171e632c1b6826b6211ce45ab85
Reviewed-by: Volker Krause <volker.krause@kdab.com>
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
| |
Change-Id: If53a4d64347cefb82e30f41204f5bb189a2377d8
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
|
|
|
| |
This is needed as also the multi-process applications need to know
whether to display the cluster widget and how big it can be rendered
Change-Id: I589439f50fa3aa60630dd7b1fb6e4008a3d1b8c2
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The UI usually doesn't stop an application, instead just the visibility
is changed and the surface items are not deleted at all.
If an application is stopped (e.g. by stopping it using the
appman-controller) we need to make sure to first run the closing animation
before we actually release the window.
Otherwise the closing animation looks broken and we leave the window
StackView in an broken state
Change-Id: I0d184283d7b0f6b41910435e328d286ed7bb1c76
Reviewed-by: Nedim Hadzic <nedim.hadzic@pelagicore.com>
|
|
|
|
|
|
|
|
|
| |
Added application which shows system
and per app usage of the system using the AM
APIs.
Change-Id: Ib6ce1ba5695d5644612bc1f3f9382b6e9b703ba9
Reviewed-by: Dominik Holland <dominik.holland@pelagicore.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cluster UI was designed for fixed size (1920x720).
It is now possible to set the cluster size in your
Style file and the Cluster should adopt to it.
Only restrictions is the proportion,
it needs to match 24:9.
Task-number: QTAUTO-110
Change-Id: I4de5c48f5ea5f65398c7dacd37d75f4a1fe314a2
Reviewed-by: Dominik Holland <dominik.holland@pelagicore.com>
|
|
|
|
|
|
|
|
|
| |
It is possible to initiate a notification using
the AM NotificationManager using the same interface
from the system UI and applications.
Change-Id: If486958bdb5a3fd37024b4430eb86ce1d3d142c0
Reviewed-by: Juergen Bocklage-Ryannel <juergen.bocklage-ryannel@pelagicore.com>
|
|
|
|
|
|
|
|
|
| |
Communication between wayland surfaces and
the system UI is more simple, without
unnecessary messages.
Change-Id: I360fb2ce61ba82d05fde4a9c0758882200df2508
Reviewed-by: Dominik Holland <dominik.holland@pelagicore.com>
|
|
* Renamed modules to imports
* Separated shared imports (needed by apps
and the system UI) and system imports, only
available to the system UI
* Moved the ApplicationManager logic from
the UI representation to its own model. The
idea is to separate UI from the logic
Change-Id: I455f0e1b4b9f9f97fe80a0dc85a355fb53bcd124
Reviewed-by: Dominik Holland <dominik.holland@pelagicore.com>
|