Comet32 Bugs or missing features ?

[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Robert G Laurin on May 10, 2019 at 08:10:57:

Found some issues in Comet 32...

Function BASE64()

Using an expression in the function will return garbage BASE64 string with the correct length.

Example:


Let String64$ = Base64(Sub(String$, 3, Len(String$) - 2), Err)   ! Encode in Base64

But, if we use a variable it works fine:

Let String$ = Sub(String$, 3, Len(String$) - 2)
Let String64$ = Base64(String$, Err)                      ! Encode in Base64

First case will generate 4/3 bytes of garbage Base64, second case will work properly. Both generate the same length.


Functions InputFile(Filepath$) and PrintFile FilePath$ FileContent$

As far as I can tell, these are the only two file function that do NOT accept a shared network path for input or output.

I know CopyFile works fine, not sure about EraseFile.

I have the feeling that I'll have to do like Comet and print to $(CATEMP) and then CopyFile to network destination. I do hope that EraseFile works on a Network Share, otherwise I don't know how I am going to get rid of processed files.

I think FindFirstFile and FindNextFile works with Network Shares... I'll double check.

Tested on Windows 7 Pro running Comet32 2018.515



Follow Ups:


Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?  

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):





Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.

[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]