Question #673348 on Sikuli changed: https://answers.launchpad.net/sikuli/+question/673348
RaiMan proposed the following answer: --- It helped me to determine that it is java.exe ... not a surprise ;-) with SikuliX, everything is Java and File handling is one of the basic support features for everything running on Java. A JVM session has many, many threads open, representing the different app-aspects and your handle-tool only connects the file-handles to the process-top-level (does not know anything of Java internal structures). On last implementation idea: Just do it the other way round: delegate your workbook-handling to a subprocess (so the file is opened there) and when coming back from there, try the delete. -- You received this question notification because your team Sikuli Drivers is an answer contact for Sikuli. _______________________________________________ Mailing list: https://launchpad.net/~sikuli-driver Post to : [email protected] Unsubscribe : https://launchpad.net/~sikuli-driver More help : https://help.launchpad.net/ListHelp
