* Removed call to abort() method in case
EnterNumberWindow's SwitchData handler
receives message that can't be handled,
what caused the phone to crash.
* Unify ApplicationCall window names
definitions.
* Code cleanup.
Fix of the issue that time on the lock screen was
getting illegible after a few hours. This change
fixes the problem by performing deep refresh
instead of fast refresh every 30 minutes. The
refresh rate can be easily changed, as it is stored
in settings database.
Split module-utils into smaller components for better dependency
management. Fix many dependencies throughout the project.
Signed-off-by: Marcin Smoczyński <smoczynski.marcin@gmail.com>
1. Prepare Pure and Bell specific `Application`
classes and add them to `app` target:
- `products/BellHybrid/apps/Application.cpp`
- `products/PurePhone/apps/Application.cpp`
2. Update `CMakeLists.txt` files.
3. Move `ApplicationBell` implementation to Bell-specific
`Application` class and remove `ApplicationBell` files.
4. Change Bell apps parent classes from `ApplicationBell`
to Bell-specific `Application` class.
5. Rename `Application` to `ApplicationCommon` in the rest of the files.
Defined separated cmake library, private and public include
directories and dependencies, isolated public headers from private,
cleaned up include paths and defined which targets depend on new
library, cleaned up include paths
This PR provides implementation of home screen notification for
`notSeen` messages received from a single number. The "single-number:
`notSeen` message notification distinct from "multiple-number"
notification with the following features:
- displaying formatted contact name
- `onActivated` it switches to respective thread window (instead of
all thread window) in `ApplicationMessages`
The PR also introduced some `ActiveNotificationsModel` code refactor
to align the implementation with `Single Responsibility Principle`
This PR adds proper notification on call notifications coming from
single number. To that end following changes have been introduced:
* extension of Notification DB record with contact_id filed
* use of `ContactRecordInterface` in `NotificationsRecordInterface`
* extension of `Increment` query to require `PhoneNumber::View`
* multiple minor changes on path from creating/handling
`NotificationsRecord` to displaying respective notification.
In initial design a `TobBar`'s SimCard icon with number is supposed
to display on the home screen only if there are two cards inserted.
Because of the hardware limitations (there is no way of telling if
there is a single or two cards inserted) the established consensus is
that home screen should not display SimCard widget unless it's
indication error state.
Although in the task description there is only home screen mentioned,
the behaviour was established for all `ApplicationDesktop`'s windows.
This PR provides following changes in notifications:
- notifications were extracted as widget for pop-up-based
locked-screen implementation
- notifications are ListView based implemented
- the most recent notification is displayed on the top of the list
Phone mode widget will be visible only on main screen, while entering
numbers or in emergency call mode. Also it will be disabled whenever NAT
widget is enabled.
Status bar SIM widget refactor
Status bar time widget recfactor
Status bar lock widget refactor
Separation of status bar time widget and desktop main window time widget
Fixed issue with wrong calculation of timezone based time
- add ChangeDateAndTimeWindow,
- extract EventTimeItem to common widgets folder
and rename it to TimeWidget,
- extract EventDateItem to common widgets folder
and rename it to DateWidget,
- replace timeWidget with common TimeWidget
in NightshiftWindow,
- refactor time setting in
DesktopMainWindow and TopBar,
- Remove dead code from EventManager
(GetNextAlarmTimestamp and HandleAlarmTrigger)
There was no refresh trigger that would cause items like clock
to display its up-to-date state while user is being inactive.
This PR solves that issue providing timer-based refresh trigger
that is dependent on user activity.
