Version 3.2.0

CommTools had no public interface from the start, although that was always intended.

To be consumed as a Tatin package, see https://tatin.dev

Version 3.1.0

• SetOnWait and UnsetOnWait added: SetOnWait establishes a function that is called whenever a
  CommTools function is about to wait for input from the user, typically for notifying the user
• Select accepts a fourth positional parameter quitFlag: it decides whether the user may enter "q"
  (for quit), independently of mustFlag. A selection can therefore be enforced while the user may
  still quit. It defaults to ~mustFlag, which is the behaviour so far
• Select accepts ranges like 3-6 (for 3 4 5 6) from the user when more than one item may be
  selected, also after a~, as in a~10-40; commas are treated like spaces
• Select does not list the syntax in the prompt anymore: the prompt offers "(Get help with ?)", and
  entering a "?" puts the choices on display again with the help injected just above the input line.
  Only what the particular call allows is mentioned
• Bug fixes
  • FindAutomationIndex, and therefore AddAutomation, threw a RANK ERROR when ∆Automation held a
    one-character ID, such as the * of Pause, and the ID in question was an alias
  • Pause threw a RANK ERROR when ∆Automation held a * row as well as an alias row
  • Pause ignored a * row as soon as there were other Pause rows: a message that matched none
    of them stopped and waited for the user
  • YesOrNo threw a RANK ERROR when ∆Automation held a one-character ID and the question had an alias

To be consumed as a Tatin package, see https://tatin.dev

Version 3.0.1

Breaking change: Select now returns ¯1 if the user enters "q" for quit. ⍬ is now only returned when the user did not enter anything (=did not make a selection).

Bug fix: the new Select-syntax (entering "q" results in ¯1) could not be automated.

To be consumed as a Tatin package, see https://tatin.dev

Version 2.1.0

• Select now supports "a~{n}" as "all but {n}"

• Select offers a new option: min-max:

  'Caption' (2 3) Select list

  is treated as "select a minimum of 2 and a maximum of 3 items. Naturally, (2 2) is most useful.

• Bug fixes

  • Select returned a one-element vector rather than a scalar when a single item was selected by automation
  • Select returned an item twice when the user, or automation, specified it more than once; duplicates are now removed

To be consumed as a Tatin package, see https://tatin.dev

Version 2.0.2

• Help polished
• Bug fixes
  • Select used ⎕ for output to the session. In 20.0 this is causing confusion when array notation is on for output. It should use ⍞.

To be consumed as a Tatin package, see https://tatin.dev

Version 2.0.1

Bug fix: The Select function printed the user input to the session.

To be consumed as a Tatin package from https://tatin.dev

Version 2.0.0

• BREAKING CHANGES:
  • You cannot specify part of a question/message/caption anymore, neither with nor without LF.
    With version 2.0 you should use an alias if you have LF in your question/message/caption or if something
    dynamic is part of it. (You can still use the wildcard character with Select for automation)
  • Automation has been redesigned. There is now only one variable in charge for automation: ∆Automation
• Helpers added for manipulating ∆Automation and gaining information about automation: AddAutomation,
  ListAutomation and FindAutomationIndex
• Testing can be done more thoroughly now thanks to the introduction of a counter on ∆Automation
• Version now uses the Tatin config as source
• Bug fixes: YesOrNo, Select and AskForText now all act correctly even when the width of the session
  is too narrow to display the question in a single line

To be consumed as a Tatin package from https://tatin.dev

Version 1.8.2

Bug fix: Select got two checks wrong

To be consumed as a Tatin package from https://tatin.dev

Version 1.8.1

• The "?"-syntax (automation variable) has been improved
• Bug fixes
  • When multiple choices with a wildcard were added to Select_Choices, only the first was returned
  • When a check function returned a 0, a default value was added to the question again
  • Left argument of AskForNumber was not checked: must be a Boolean

To be consumed as a Tatin package from https://tatin.dev

Version 1.8.0

• Select now supports the wildcard character (*) not only at the end but also at the beginning of the second column of the SelectChoices variable
• Now all functions return a full path to a global variable that can be used for automation when the right argument is a scalar question mark (?)
• Documentation polished
• Test cases refitted

To be consumed as a Tatin package from https://tatin.dev