I was just using it as an example to show how one that was optional "might" look... I know that one is actually mandatory.Bob Hansen wrote:In your new format proposal you show easypatterns as optional, but I understand it is mandatory for 0/1, so it should also be bolded.
Hi Bob,existing format is just fine wrote:HTTPRequest>URL,[LocalFilename],Method,[POST_Data],Result_Variable[,ProxyServer,ProxyPort,ProxyUsername,ProxyPassword]
Retrieves a web document via the HTTP protocol using either GET or POST methods.
URL: URL of document to retrieve
LocalFileName: Optional (may be left blank) - local file to save response to.
I should have looked a bit more... as shown by another out-take from the Help File above, the existing format is just fine... optional parameters that are not "at the end of the list"... for example, [LocalFileName] above... are also handled by enclosing them in square brackets.

However the idea to have the commands error out with an error message if a required parameter is omitted is a good one... and it came to light because of your post so it was well worth the time.