It has been quite some time since I updated this blog, but for a good reason, I worked quite hard on the MXPAD selection integration and flow of work, but first thing first:
version 3.0.206 is out with updated documentations and examples.
So now that it is out my system lets talk about the modifications to Mission-X:
- MX-Pad now supports selection input from the simmer (4 options overall). This can be done only by script therefore downloading and reviewing the code example will make it easier to understand the flow.
- While working on the selection demo I re-thought some of the limitation or "complexity" with "mxpad" and "message" handling. Therefore I decided to do some optimizations to make the flow easier.
From MXPAD management:- old: We had to start the mxpad from a task and then disable the task so it won't call the same command again.
new: Plugin stores current running "mxpad name", therefore it won't "execute/start" it if it is already running. No need to disable the task. - Due to the change in how to start "mxpad", it means we can have only one "task" in an "objective" that we will manage from the "mxpad" script.
Unfortunatelly that raised a new issue - an "mxpad" script can't modify "task" state, so your goal could never progress.
- old: We had to start the mxpad from a task and then disable the task so it won't call the same command again.