Digital Workshop

Hi

Is there any way in a project to close all .txt files using a wildcard? In order to get the delete file action to work without script editor error messages, it appears these files, viewer-created in the Opus pub and opened in runtime to store data to disk files, need to be closed first. So far, my work-a-round has been to exit and re-start the pub after the delete action to "clear" it and prevent error messages, object not found type, which then lead to script failure.

Any ideas would be appreciated.

Kind Regards,
Stephen

Hi

I'm continuing to experiment with trying to script a close file action. I'm unsure if you set up the script to close the actual file or set it up to close the textobject created by the openfile action.

So for the file myText.txt, which is opened as
var textObj = OpenFile("c:\\myText.txt")

do I use the file pathname to somehow script ?:

("c:\\myText.txt").Close()
(I'm unsure how to correctly specify the file's pathname, here. I also suspect this won't work.)

or can I effectively close the file by scripting?:

textObj.Close()

I'm confused as to how to close a file opened by a script

var textObj = OpenFile("c:\\myText.txt").

Part of my confusion is that if I were to use the standard Opus closefile action, it would specify the actual file-to-close's pathname and not a variable like textObj.

Any help would be appreciated.

Kind Regards,
Stephen

This one - you need to close the file object. The location and name of the file has no bearing on it.

Thanks Duncan.

I had actually experimented with this, as part of trying everything conceiveable. The open file scripts are individualized for each object so the first object textobj variable is simply textobj, the second is named textobja, third, textobjb and so forth. There are 50 or so objects each with their own variation a-w and aa-ww.

The experiment involved textobj.Close() and a second script textobja.Close(). Then the 2 actual .txt files, which are opened as the textobj and textobja variables, found in SYSTEM_DOCUMENTS_DIR foldername\pos.txt and foldername\posa.txt, were each deleted using a standard Opus delete file action. (I couldn't figure out how to delete these files using script-the standard action had to suffice.)

Irregardless, this should have closed and cleared out the storage files. Returning to the page to recreate new data and storage, etc. (starting fresh), the script editor now showed error messages upon save and reset: object(s) not found.

I'm not knowledgeable about why, but it almost seems that absent exiting the entire pub and re-booting it, something is held in a cache-like place, causing error messages (and eventually script failure).

Is there any effective way to close, clear, delete these .txt files and not have them cause error messages and eventual script failure?

Thank you for your help.

Kind Regards,
Stephen