Hi Sterling,
You are correct that it defaults to the default event queue. Aditi, Marko, and
I discussed this and we decided that it would simplify the documentation to
tell the apps to explicitly make the call to mgmt_evq_set (even when it chooses
to use app's default event queue) so we don't have the special cases (oicmgr vs
newtmgr, default event queue vs a different queue etc) to explain . The
document does tell the user that it can specify it's default event queue in the
call, and that it doesn't have to create a dedicated event queue and task for
this purpose.
Thanks,
Wanda
On Friday, January 27, 2017 6:46 PM, Sterling Hughes
<sterling.hughes.pub...@gmail.com> wrote:
These should default to the default event queue, no?
> On Jan 27, 2017, at 6:27 PM, Wanda Chiu (JIRA) <j...@apache.org> wrote:
>
> Wanda Chiu created MYNEWT-576:
> ---------------------------------
>
> Summary: Update apps that use newtmgr framework to explicitly set
>the event queue with mgmt
> Key: MYNEWT-576
> URL: https://issues.apache.org/jira/browse/MYNEWT-576
> Project: Mynewt
> Issue Type: Bug
> Components: Misc
> Affects Versions: v1_0_0_beta1
> Reporter: Wanda Chiu
> Assignee: Sterling Hughes
> Priority: Trivial
> Fix For: v1_0_0_rel
>
>
> The tutorial to enable Newt Manager in Any App indicates that the app must
> call the mgmt_evq_set to specify the event queue that mgmt uses to receive
> newtmgr request events. We need to update the apps that use the newtmgr
> framework to make this call.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.4#6332)
