Check for active .exe using iLogic? -Voidtools Everything causing issues

Check for active .exe using iLogic? -Voidtools Everything causing issues

FrazzledInventor
Explorer Explorer
831 Views
2 Replies
Message 1 of 3

Check for active .exe using iLogic? -Voidtools Everything causing issues

FrazzledInventor
Explorer
Explorer

Hi all,

 

Long time lurker but haven't found a solution to this problem.

We were recently made aware of a brilliant search tool 'Everything' published by Voidtools. Works great, far faster than Windows Search and it has become an important part of speeding up our day. Regardless of any potential problems with server structure, we have found a major shortcoming: it doesn't play nicely with Inventor.

 

Refer to these issues:

https://knowledge.autodesk.com/support/inventor/troubleshooting/caas/sfdcarticles/sfdcarticles/VoidT...

https://knowledge.autodesk.com/support/inventor/troubleshooting/caas/sfdcarticles/sfdcarticles/Error...

 

I understand that the way the tool works is basically by pinging the master file register of the server, and gives accurate search results in real time. The problem comes when there are multiple file operations happening quickly, like initially saving multiple parts in new assembly, likely too difficult for a process trying to keep an eye on the all files in a register.

Even saving single files seems to have issues; the quick creation of FilenameX.NewVer.ipt as part of the ordinary save process still seems to be too much for Everything.

The invariable result is the corrupted files described in the links above.

 

But! Great news. I have found though that so long as Everthing.exe is not running in the foreground (or background, an option enabled by default but a simple setting change) life can continue as normal.

 

To reduce operator error, I am looking for a way to check that Everything.exe is not running. I assume iLogic is the solution:

  • Use "Before Save" trigger to run iLogic code
  • If Everything.exe is found to be running: cancel the save operation, and open a dialogue box suggesting the user close Everything.exe
  • If Everything.exe is not found to be running, carry on the save operation as normal.

I have been able to chop up various iLogic snippets so far but haven't found anything close to this sort of test to date.

Is it possible to perform the above process using iLogic? If so, and it's not too difficult, I'd be incredibly grateful for sample code.

 

Any and all help appreciated.

Cheers

832 Views
2 Replies
Replies (2)
Message 2 of 3

JelteDeJong
Mentor
Mentor

i don't have this exact tool therefore i wrote an example that checks if notepad is running. It's difficult to stop a save action enterally but a message box will stop the process. that time can be used to close the program manual. But its also possible to kill the program automatically. 

Dim pros As Process() = Process.GetProcessesByName("Notepad")
If (pros.Length > 0) Then
	Dim result As MsgBoxResult = MsgBox("'Everything' is running. Do you want to close it?", MsgBoxStyle.YesNo, "Kill the prosess")
	If (result = MsgBoxResult.Yes) Then
		For Each pro As Process In pros
			pro.Kill()
		Next
	End If
End If

Jelte de Jong
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

EESignature


Blog: hjalte.nl - github.com

Message 3 of 3

jaquinYX4QT
Explorer
Explorer

Hi, I know it's been a while for this topic. Thanks for the information above. We started using Everything recently and experienced the issues mentioned above with Inventor.

In Everything -> Tools -> Options, there's a section named "Exclude". In the Exclude files field, you can enter a wildcard filter list of files to exclude. I typed the following text to exclude Autocad .dwl files, Inventor .NewVer. and the Database files .db:

*.db;*.dwl;*.dwl2;*.newver.

I'm not sure yet if this can prove useful, but it does not hurt to give it a try.