I have to give a huge shout out to
InspectorJester what a smart kid, with his help I was able to get a Form Editor, functioning popup at the beginning of my program to choose different ops to run inside the program. I hope he takes the time to share with everyone that does not know this. Now I myself made it look fancy, but he helped me get it to function. Thank You Jester. Not done with it yet, but there's a taste of my finally functional buttons
I have some recordings set up I can post a link to detailing the process.
I'm thinking YouTube? I still have to do some editing, so it won't be today, unfortunately.
Anyway, I strictly use the Form Editor to make forms.. Pretty straightforward thinking.
I'm not certain about this for those who run PC-DMIS from a custom GUI (such as through VBS, C, or otherwise); my process uses native PC-DMIS code, assignments and the like.
There have been a few posts regarding having one PC-DMIS program allow the user to choose between multiple operations, select whether or not to manually align first, and general "jumping around the program" nonsense. I love it!
So, the video I'm compiling together describes using forms to set up some buttons and the like, and choose between multiple operations.
I have to measure Blanking, Secondary, and Plating operations, depending on where the part is in the process. I'd like to not measure the blanking features if I'm measuring secondary, or skip the secondary if I'm measuring blanking. If I measure plating, I'd like to measure the whole part.
Instead of having a hundred operator comments, I wanted to have everything in a nice user interface; forms seemed the best choice.
-------------
A cool thing about forms is you can set defaults. For example, you're the only programmer. You'd like to have your clock number, name, or what have you run every time; it'd be tedious to re-enter it
every time.
Or, you're testing the program, and you're not going to change how the form is set up. Why re-enter it every time if you don't have to?
-------------
Anyways, that's a lot of talk from me and not a lot of substance. I'll be working on posting everything, drafting up some nice little paragraph or something, in the coming days (as I don't have them with me today )
Also, interesting note about the buttons
KIRBSTER269; I'll have to try that. Mine are rather boring!
I have some recordings set up I can post a link to detailing the process.
I'm thinking YouTube? I still have to do some editing, so it won't be today, unfortunately.
Anyway, I strictly use the Form Editor to make forms.. Pretty straightforward thinking.
I'm not certain about this for those who run PC-DMIS from a custom GUI (such as through VBS, C, or otherwise); my process uses native PC-DMIS code, assignments and the like.
There have been a few posts regarding having one PC-DMIS program allow the user to choose between multiple operations, select whether or not to manually align first, and general "jumping around the program" nonsense. I love it!
So, the video I'm compiling together describes using forms to set up some buttons and the like, and choose between multiple operations.
I have to measure Blanking, Secondary, and Plating operations, depending on where the part is in the process. I'd like to not measure the blanking features if I'm measuring secondary, or skip the secondary if I'm measuring blanking. If I measure plating, I'd like to measure the whole part.
Instead of having a hundred operator comments, I wanted to have everything in a nice user interface; forms seemed the best choice.
-------------
A cool thing about forms is you can set defaults. For example, you're the only programmer. You'd like to have your clock number, name, or what have you run every time; it'd be tedious to re-enter it
every time.
Or, you're testing the program, and you're not going to change how the form is set up. Why re-enter it every time if you don't have to?
-------------
Anyways, that's a lot of talk from me and not a lot of substance. I'll be working on posting everything, drafting up some nice little paragraph or something, in the coming days (as I don't have them with me today )
Also, interesting note about the buttons
KIRBSTER269; I'll have to try that. Mine are rather boring!
)