How to stop an iLogic loop with the keyboard

[Anonymous]

Hi,

Is it possible to stop an infinite loop when running an iLogic rule?

Thanks,

Pascal Langlais

[MjDeck · Accepted solution]

I'm sorry, it's not possible.  We are planning to add that in a future version.  At the present time, all you can do is use the Task Manager to kill the Inventor process.

[Anonymous]

Thank you Mike for the answer.

Pascal

[fsanchou]

Is it possible to do so in the new version?
What are the debugging capabilities with iLogic?

[Anonymous]

Mike,

Can you let me know why has this not been addressesed? It has been 2 years since this thread started and that you have known about it. You have replied the same in other threads about the same subject. If you can do it in VB why then could you not do it in iLogic? Thanks in advance for your input.

[Anonymous]

Hi,

I'm also wondering why it hasen't been adressed yet? It's a VERY helpfull tool. Or has it been adressed in the 2015 release?

[fsanchou]

Hi, Unfortunately, I haven't read anything new for version 2015

[Anonymous]

Wonder if the inability of iLogic loops to be stopped will be resolved in the 2017 version? 

[metamere]

It looks like this is still an issue in the 2017 version.  Pretty sad.  Debugging is still an arduous process because there is no way to step through your code. At least you can finally save an external rule without it automatically running.

[Anonymous]

---

@MjDeck wrote:

I'm sorry, it's not possible.  We are planning to add that in a future version.  At the present time, all you can do is use the Task Manager to kill the Inventor process.

---

Almost six years later...whatever happened?  

No matter, here's a link to a "If Then  Then That" blog post discussing a  debugging workflow utilizing DebugView.

[MjDeck]

We're looking at it, but it's not easy. We're also looking at adding debugging capabilities.

[Rob67ert]

Hope it will be added in the 2018 version.

[Anonymous]

This is a much needed feature, and should be simple to implement.

[c_stulz]

I'm allthough waiting for it.

I tried in Inventor 2019., but I found no way.

---

---

[thopper]

This is ridiculous!!! No way to break a loop in an Ilogic routine! You could break a program on a DEC PDP 11-70 40 years ago with crtl+C! I just lost 2 hours work because of Autodesk being too inept to put the most basic debug tool in Ilogic.

PS never use a While loop until they fix this issue!

[MechMachineMan]

Do you put screws into boards with a hammer as well?

If the tool you are using doesn't give you the results you want, maybe you should look at a different tool.

In this case, the VBA does have step functionality and debugging, so it's a lot nicer of an option.

That being said, it's bad programming practice to put an infinite loop in to begin with, so if you do not know what you are doing, you should put in proper checks in your program to prevent it from happening (ie; a loop limit of x).

[thopper]

At least a common claw hammer has a removal tool on the other side. All developers have created infinite loops during development. That is why debug tools exist.   You know nothing about the application I am working. VBA is obsolete and is not an option for this application for that and several other reasons. 

How or why a bug was creating in some code or using correct programming nomenclature is not the issue here. The lack of the most rudimentary debug tools in Ilogic is the issue. 

[MechMachineMan]

The iLogic environment wasn't designed as a fully comprehensive IDE. It was designed as a quick tool for customization, that has experienced quite a bit of scope creep over the years.

If you want debugging and don't want vba, then use visual studio as your IDE to do the programming.

Again, sometimes you are better off adapting to make do with the way things ARE instead of crying about how they AREN'T.

The Idea Station is the proper place to provide feedback regarding the program.

[bradeneuropeArthur]

There are possibilities to stop the command. I will take a look and come back to it, ok?

[Anonymous]

---

@MechMachineManwrote:

The iLogic environment wasn't designed as a fully comprehensive IDE. It was designed as a quick tool for customization, that has experienced quite a bit of scope creep over the years.

If you want debugging and don't want vba, then use visual studio as your IDE to do the programming.

Again, sometimes you are better off adapting to make do with the way things ARE instead of crying about how they AREN'T.

The Idea Station is the proper place to provide feedback regarding the program.

---

1. Yes, iLogic has experience scope creep. That's because it gives the users the ability to do the coding that is lacking from the main product.

2. We can't always debug in another environment. Often the variables and functions we need to work with are specific  to the CAD models we are working on and need to be accessed directly.

3. Don't tell us where we need to complain. We are looking for a solution to the problem. This may belong in the idea station, but it also belongs here because we are looking for a solution that someone else may have already found.