On Thu, 2017-04-13 at 12:35 +0100, Colin Helliwell wrote: > > On 13 April 2017 at 12:07 Colin Helliwell <colin.helliwell@ln-syste > > ms.com> wrote: > > > > Hi, > > This thread turns out to be relevant to the latest in my battle > > with Cinterion modules. Their EHS5 doesn't support AT^SPIC, but it > > turns out it does support the CSIM commands used by the telit > > plugin - https://developer.gemalto.com/tutorial/how-query-pin-count > > er-ehsx > > > As a follow-on musing, does MM have mechanisms (or examples) for > cascaded fallback procedures - i.e. "Try to do this [set of > operations] using Method A, and if an an 'un-supported' error comes > back, then try Method B".....? > Is it just (ha!) a case of expanding out the 'context step' code > flow?
Right, if you have [set of operations A] and then [set of operations B] and need to jump to B if some part of A fails, that's usually done through the "context step" pattern that you've seen. That pattern keeps all the flow decision logic in one place, rather than having it sprinkled around a bunch of different functions in the file. Dan _______________________________________________ ModemManager-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
