Prevent auto-update when filling form

Prevent auto-update when filling form

sultan_mustun
Advocate Advocate
772 Views
3 Replies
Message 1 of 4

Prevent auto-update when filling form

sultan_mustun
Advocate
Advocate

I have a form, which is used to fill out the details of a nameplate.
The parameters in the form are Custom iProperties, which are used in an Emboss function.

 

sultan_mustun_0-1716285972421.png

 


The issue:
Every time I change a value, it takes a while to update the model, and only after that I can update the next parameter and again wait for it to update the model.
Isn't there an option to prevent auto-update of the modelling functions, until I click "DONE" on the form?
Something like we have in the Functions window:

sultan_mustun_1-1716286076720.png

 

Thank you.

0 Likes
Accepted solutions (2)
773 Views
3 Replies
Replies (3)
Message 2 of 4

WCrihfield
Mentor
Mentor
Accepted solution

Hi @sultan_mustun.  If this was a 'global' iLogic Form, then it would not update anything until you either clicked Apply, Done, or something similar, because a 'global' form is not 'connected' to any specific document like an 'internal' one is.  When using an internal iLogic Form (saved within an Inventor document), then it is 'connected' to that document, and will immediately update that document when things change within that form.

Wesley Crihfield

EESignature

(Not an Autodesk Employee)

Message 3 of 4

Curtis_Waguespack
Consultant
Consultant
Accepted solution

Hi @sultan_mustun ,
Changing the form to use the OK/Cancel/Apply buttons is probably what you are looking for here. There are some other ways to create our own buttons using rules, and then hacking those buttons by editing the underlying global form XML file, but that seems beyond what you're looking for.

 

Curtis_Waguespack_0-1716302674296.png

 

I hope this helps.
Best of luck to you in all of your Inventor pursuits,
Curtis
http://inventortrenches.blogspot.com

EESignature

Message 4 of 4

sultan_mustun
Advocate
Advocate

Thank you both for your answers.

@Curtis_Waguespack this solved my issue, thank you.

@WCrihfield thank you for the explanation, I will keep this in mind for future projects.