Age | Commit message (Collapse) | Author | Files | Lines |
|
Avoid crashing on various platforms, by not setting any argument at all.
Bug-AGL: SPEC-3843
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: Ifb082b95fd6ebc71e863b843c9fd895f5f7efdde
|
|
The fake subscribe mechanism failed to account for the client context,
which is bound to the afb_req_t of the client itself, and only
dealing with the client list. This effectively means we can't
really register (a/an automated) callback function to remove the
appid from the client list once the application has been legally
terminated/stopped.
This adds a check to verify, for the showWindow verb, if the application
is still found to be running, and return the appropriate value in case
that is not case. This should determine to start the application and fix
the issue.
Bug-AGL: SPEC-3796
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: Ia828e1ec374bf3bed21c52814721074c01f16691
|
|
The subscribe mechanism requires that the client itself performs the
subscribe (it assumes a unique, distinct afb_req_t type in order to
create the client context) and attempting to handle one,
automatically would not really work, so only use it (the fake sub mechanism)
the keep track of application w/ the help of the client_list.
Bug-AGL: SPEC-3796
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: I783614e1db83280878b77b786e4f80fccd1a74a1
|
|
The subscribe verb was used in the past to keep track of applications,
which was done in background with the help of event handlers. As
that no longer happens we keep track of the client and its clientCtx
when starting directly from the homescreen binding, faking the subscribe
logic.
As the afb_req_t object is no longer in scope when the async callback
handler returns, we do it before doing the call to af-main, and assume
that we'll succeed.
We use the async callback handler to verify if the application was
indeed started but any application crashing afterwards will require an
additional check performed, as it will found in the hash table of
clients.
Bug-AGL: SPEC-3524
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: I0e417dc5f2953947cd27ca551c0d2a2af5c57e6d
|
|
Bug-AGL: SPEC-3524
Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: I80a7bac4244e62f49ab4bf068476ad4e888085f1
|
|
1. using binder log macro instead of HMI_LOG.
2. unify log using level as below:
AFB_ERROR: fatal error or serious error may occur.
AFB_WARNING: input parameter error or not serious error.
AFB_NOTICE: alert sth.
AFB_INFO: print input argument or sth else.
AFB_DEBUG: prompt for calling location.
3. delete hmi-debug.h.
Change-Id: I203864ced39c418d2f792faa50ab2c009deb9d02
Signed-off-by: wang_zhiqiang <wang_zhiqiang@dl.cn.nexty-ele.com>
|
|
1.start application in showWindow.
2.add "getRunnables" verb.
3.handle "application-list-changed" event from afm-main and add "application-list-changed" event.
Bug-AGL: SPEC-2188
Change-Id: I619b97424d20af373a945ff502a8133339916923
Signed-off-by: wang_zhiqiang <wang_zhiqiang@dl.cn.nexty-ele.com>
|