Hi,
as previously explained the numeric range of signals for which mcSignalWait() will work is limited to 5bits ie 0-63. That is what it is.
I stumbled over it and you are right there is no notes or documentation covering it, I have asked NFS to add one line to the API.chm but to no avail.
For this reason I have commented before that NFS does not appear to act on specific documentation suggestions.
Remember I have a Mach4Hobby license and for a Hobby User I can expect some out of the box functionality.
Good luck with that! In this instance NFS is not to blame however, the modern programming paradigm is that an object and its action are separate and
Mach4 follow that paradigm. What Mach4 is very very good at is being programmatically flexible but that in turn requires that you program it to suit
your particular needs.
Everything I have done so far was by trail and error or by looking in the forum
I agree, I've had exactly the same experience.
The documentation is for sure rubbish
I would not put it that strongly but certainly the documentation is out of date. smurph has explained that generating technical documentation is a very
resource/time intensive excerise. NFS has not taken up that challenge yet, but have persued further development....things like PMC, the probing module, the Zero Brane
editor....all of these things are new. They would not exist if NFS poured its resources into documentation say.
Craig