[v1.7.3.2] Minor notes

[Pfeil]

Added, '{STATE_JOYSTICKSHORTCUTS}' that renders "1" if joystick button shortcuts are on, "0" if not.
       Somehow this was missed long ago when these tokens were added.

This token appears to be identical in function to the existing "{STATE_JOYSTICKBUTTONS}", though this syntax is more consistent with the "{STATE_SHORTCUTS}" and "{STATE_MOUSESHORTCUTS}" tokens.

{STATE_SHORTCUTS} - This token tests to see if VoiceAttack's shortcuts are enabled. If shortcuts are enabled, the replaced value will be "1". Otherwise, the replaced value will be "0".

As this returns the state of keyboard shortcuts(rather than a collective state of all shortcuts), would it be clearer if this read "VoiceAttack's keyboard shortcuts"?

-  Added, 'GetSpeechRecordingDeviceMute()' function to VA proxy object - this allows you to query whether
       or not the recording device that the speech engine is using is muted or not.
   
    -  Added, 'SetSpeechRecordingDeviceMute(Boolean Mute)' function to VA proxy object.  This allows you
       to mute/unmute the Windows recording device that the speech engine is currently using.

These methods have not been added to the autocomplete feature of the Inline Function editor


The following items from the v1.7.3.2 changelog are not documented in VoiceAttackHelp.pdf(As mentioned in Discord):

-  Added, 'Mute Speech Recording Device' to system menu.  This mutes/unmutes the recording device that
       the speech engine is currently using.
       
    -  Added, 'GetSpeechRecordingDeviceMute()' function to VA proxy object - this allows you to query whether
       or not the recording device that the speech engine is using is muted or not.
   
    -  Added, 'SetSpeechRecordingDeviceMute(Boolean Mute)' function to VA proxy object.  This allows you
       to mute/unmute the Windows recording device that the speech engine is currently using.
       
    -  Added, 'Speech Engine Recording Device' as an option to, 'Recording Device' on the 'Set Audio Level'
       screen.  This is so you can just specify whatever the speech engine is currently using without
       having to know exactly what device it is.

EDIT: All resolved; Checked with v1.7.3.9

[Gary]

This token appears to be identical in function to the existing "{STATE_JOYSTICKBUTTONS}", though this syntax is more consistent with the "{STATE_SHORTCUTS}" and "{STATE_MOUSESHORTCUTS}" tokens.

It is - I didn't see it because the documentation is actually in the joystick state token reference.  What will happen is that I will update the documentation to say that the token has been replaced with {STATE_JOYSTICKBUTTONS} (but leave the processing alone so that it wont break anything in place).

As this returns the state of keyboard shortcuts(rather than a collective state of all shortcuts), would it be clearer if this read "VoiceAttack's keyboard shortcuts"?

Yeah... this existed before there were other shortcut tokens - fixed up.

Token documenation is a mess - needs to be organized and not just thrown in as 'somewhat like the order they were added'.

These methods have not been added to the autocomplete feature of the Inline Function editor.

They are now   Finally set up the proper spacing between parameters while I was in there, too.


The, 'Mute speech recording device' is mislabeled in the change log and is actually, 'Mute Speech Recognition Device'. The other items have been added