-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add migrating to 8.0 guide #133
Conversation
docs/Migrating to Newer SDL Versions/Migrating SDL Core 7.1 to 8.0/index.md
Outdated
Show resolved
Hide resolved
docs/Migrating to Newer SDL Versions/Migrating SDL Core 7.1 to 8.0/index.md
Show resolved
Hide resolved
<function name="UnsubscribeButton" messagetype="response"></function> | ||
|
||
``` | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should probably include a section for the behavior changes for the phone call event here:
OnEventChanged (PHONE_CALL)
The behavior of the PHONE_CALL
event was changed to only affect the audioStreamingState
of an app. Rather than automatically deactivating the active app, SDL Core will now only change the audioStreamingState
of all apps to NOT_AUDIBLE
when BC.OnEventChanged(PHONE_CALL, active=true)
is sent, leaving each app's hmiLevel
unchanged. This allows the HMI to start a phone call in the background without leaving the app screen, if desired.
The HMI can still control the hmiLevel
of the app during a phone call event by sending BC.OnAppDeactivated(appID)
and BC.OnAppActivated(appID)
where appropriate.
Co-authored-by: Collin <iCollin@users.noreply.github.com>
@@ -87,6 +87,9 @@ | |||
}, | |||
{ | |||
"name": "Migrating SDL Core 7.0 to 7.1" | |||
}, | |||
{ | |||
"name": "Migrating SDL Core 7.1 to 8.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might want to also add a link to this guide in the overview page https://smartdevicelink.com/en/guides/core/overview/#migrating-to-newer-sdl-versions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
docs/Migrating to Newer SDL Versions/Migrating SDL Core 7.1 to 8.0/index.md
Outdated
Show resolved
Hide resolved
docs/Migrating to Newer SDL Versions/Migrating SDL Core 7.1 to 8.0/index.md
Outdated
Show resolved
Hide resolved
docs/Migrating to Newer SDL Versions/Migrating SDL Core 7.1 to 8.0/index.md
Outdated
Show resolved
Hide resolved
docs/Migrating to Newer SDL Versions/Migrating SDL Core 7.1 to 8.0/index.md
Outdated
Show resolved
Hide resolved
The parameters in the notification have also changed. | ||
|
||
The parameter `requestID` is used instead of appID to identify which specific request should have its timeout extended. | ||
|
||
The parameter `methodName` should include the interface name and the rpc. For example: `”TTS.Speak”`. | ||
|
||
The parameter `resetPeriod` allows the HMI to specify how long Core should delay the application request’s timeout. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The parameters in the notification have also changed. | |
The parameter `requestID` is used instead of appID to identify which specific request should have its timeout extended. | |
The parameter `methodName` should include the interface name and the rpc. For example: `”TTS.Speak”`. | |
The parameter `resetPeriod` allows the HMI to specify how long Core should delay the application request’s timeout. | |
The parameters in the notification have also changed: | |
- The parameter `requestID` is used instead of appID to identify which specific request should have its timeout extended. | |
- The parameter `methodName` should include the interface name and the rpc. For example: `”TTS.Speak”`. | |
- The parameter `resetPeriod` allows the HMI to specify how long Core should delay the application request’s timeout. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JackLivio please let me know if you have any questions about my feedback. Thanks!
docs/Migrating to Newer SDL Versions/Migrating SDL Core 7.1 to 8.0/index.md
Outdated
Show resolved
Hide resolved
docs/Migrating to Newer SDL Versions/Migrating SDL Core 7.1 to 8.0/index.md
Outdated
Show resolved
Hide resolved
docs/Migrating to Newer SDL Versions/Migrating SDL Core 7.1 to 8.0/index.md
Outdated
Show resolved
Hide resolved
docs/Migrating to Newer SDL Versions/Migrating SDL Core 7.1 to 8.0/index.md
Outdated
Show resolved
Hide resolved
docs/Migrating to Newer SDL Versions/Migrating SDL Core 7.1 to 8.0/index.md
Outdated
Show resolved
Hide resolved
docs/Migrating to Newer SDL Versions/Migrating SDL Core 7.1 to 8.0/index.md
Outdated
Show resolved
Hide resolved
docs/Migrating to Newer SDL Versions/Migrating SDL Core 7.1 to 8.0/index.md
Outdated
Show resolved
Hide resolved
docs/Migrating to Newer SDL Versions/Migrating SDL Core 7.1 to 8.0/index.md
Outdated
Show resolved
Hide resolved
docs/Migrating to Newer SDL Versions/Migrating SDL Core 7.1 to 8.0/index.md
Outdated
Show resolved
Hide resolved
docs/Migrating to Newer SDL Versions/Migrating SDL Core 7.1 to 8.0/index.md
Outdated
Show resolved
Hide resolved
Co-authored-by: theresalech <theresa@livio.io> Co-authored-by: Shobhit Adlakha <ShobhitAd@users.noreply.github.com>
Add information to highlight important integration updates. This guide includes updates to the accepted environments, configuration options, and HMI API updates integrators will need to take note of.