Wildcards in variables

Hello!

Sorry if this is posted before but I am could not find anything :S

I need to delete some files ending in .probe with pcdmis in c:\temp and I would like to use a variable to define all files of this type. Is this possible to do with just the assign variable command or from the delete file command directly? Thanks in advance!

JEFMAN over 1 year ago

Something like this ?

DO/
V1=FILE/DIALOG,Choose a file to delete.
V2=FILE/EXISTS,V1
IF/V2<>0
COMMENT/OPER,File exists. Ready to delete.
FILE/DELETE,V1
END_IF/
C1 = COMMENT/YESNO,NO,Full Screen=NO,
Do you want to delete another file ?
UNTIL/C1.INPUT=="NO"

constadin over 1 year ago
Something like this ?

DO/ V1=FILE/DIALOG,Choose a file to delete. V2=FILE/EXISTS,V1 IF/V2<>0 COMMENT/OPER,File exists. Ready to delete. FILE/DELETE,V1 END_IF/ C1 = COMMENT/YESNO,NO,Full Screen=NO, Do you want to delete another file ? UNTIL/C1.INPUT=="NO"

Hmm not quite. I need PCDMIS to auto delete all "*.fileextension" from a specific folder without asking anything or forcing the operator to choose. For example, for *.txt files in C:\test I execute the program and it auto deletes 1.txt , 10.txt, whatever.txt etc.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
vpt.se over 1 year ago

https://docs.hexagonmi.com/pcdmis/2023.1/en/helpcenter/mergedProjects/core/25_inputoutput_topics/Deleting_a_File.htm?rhhlterm=file%20commands&rhsyn s=%20

Maybe:
ASSIGN/MYVAR="*.TXT"
FILE/DELETE, MYVAR

...but you would need to specify the entire path.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
constadin over 1 year ago

https://docs.hexagonmi.com/pcdmis/2023.1/en/helpcenter/mergedProjects/core/25_inputoutput_topics/Deleting_a_File.htm?rhhlterm=file%20commands&rhsyn s=%20

Maybe:
ASSIGN/MYVAR="*.TXT"
FILE/DELETE, MYVAR

...but you would need to specify the entire path.

I tried it earlier and does not work using the full path ofcourse. In the expression builder there is a ** symbol that I fail to understand what is doing from the help file but even that does not work within or without "". I think I may have exhausted all "**", "*", *, ** options but nothing seems to work
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
JEFMAN over 1 year ago
Ok, that's not what you want, but it could work on Excel.
If someone here can add "excel.application", and any information to make it work on the demon... ?

There's also a delete to add after the msgbox.

Sub AfficherInfoDossier() specdossier = "C:\temp" Dim fs, f, s Set fs = CreateObject("Scripting.FileSystemObject") Set f = fs.GetFolder(specdossier) Set fc = f.Files For Each f1 In fc s = f1.Name If Right(s, 4) = ".txt" Then MsgBox (s) End If Next End Sub
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
bfire85 over 1 year ago

Why don't you set something up in Windows Scheduler and run a task, piggybacked off a powershell to delete files with specific file extensions? Then set it up on a schedule.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
constadin over 1 year ago

Why don't you set something up in Windows Scheduler and run a task, piggybacked off a powershell to delete files with specific file extensions? Then set it up on a schedule.

The issue is with pcdmis and inspect. Inspect is creating some info files (unrelated to pcdmis and its fanctionality) and updating them at the end of the routine. For whatever reason I am getting an error message that prevents the routines to be completely finished saying that the file (*whateverprobeIamcalibrating*.probe) is being used by another procedure. I saw that if the file exists on the folder on startup and later on is deleted, inspect recreates it at end of routine with no error message. When I autocalibrate in a program 1 single probe I can have pcdmis delete the file but when I am autocalibrating a lot or if others do it without knowning be4hand which probes, it can be messy.

I know I can create a bat file and a task schedule or even a script from within pcdmis but it would be make so much more sense if I could ask a delete command for all *.probe files
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
constadin over 1 year ago in reply to JEFMAN

Creating scripts beats the point :P
I find it strange that a * wildcard cannot be used in such commands / tools or even variables!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Neil Challinor over 1 year ago in reply to constadin

If you want to keep as much code as possible within the PC-DMIS routine, a batch file is probably the best way to handle this. Use the File I/O commands to create and populate it, then execute it as an external command. You can then delete the batch file after it's been executed if you so wish.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Neil Challinor over 1 year ago in reply to constadin

Something like this..

            ASSIGN/FIL_PATH="C:\\TEST\\"
FPTR       =FILE/OPEN,C:\Users\Public\Documents\Hexagon\PC-DMIS\Del_Txt.bat,WRITE
            FILE/WRITELINE,FPTR,"del "+FIL_PATH+"*.txt"
            FILE/CLOSE,FPTR,KEEP
            COMMENT/OPER,NO,FULL SCREEN=NO,AUTO-CONTINUE=YES,TIME DELAY=1,OVC=NO,
            Creating batch file
            EXTERNALCOMMAND/NO_DISPLAY, WAIT ; C:\USERS\PUBLIC\DOCUMENTS\HEXAGON\PC-DMIS\DEL_TXT.BAT
            COMMENT/OPER,NO,FULL SCREEN=NO,AUTO-CONTINUE=YES,TIME DELAY=1,OVC=NO,
            Deleting text files
            FILE/DELETE,C:\USERS\PUBLIC\DOCUMENTS\HEXAGON\PC-DMIS\DEL_TXT.BAT

Just change the FIL_PATH variable to be whatever folder you need to target.