Hi guys, welcome back to my channel. This is a series of videos about SolidWorks scripting in Python, and in this video I

am going to cover fancy arguments in SolidWorks scripting. Sometimes we face some fancy arguments in Python that we don't have in

Python, but we have them in Visual Basic. So I'm going to call them 'fancy arguments'. I'm going to show you the differences

between SolidWorks and Visual Basic. For that, create a new part file and create a simple part in the desktop with meaningful names. Going to open it.

Okay, let's see the first difference is in this line. I'm going to copy and paste it here as we

talk about it in the previous video. We don't have this line directly in Python, so we need to translate it, and it will

be this line instead of this line in Visual Basic. So this is the difference between Visual Basic and Python. The second difference

is fancy arguments. For example, I'm going to show you a function for saving this file. I'm going to save it first on my desktop

with the name 'part.sldprt'. Okay, and going to open API help and search for 'SaveAs' method. As it says here, save the

current document. So it gets three arguments: options, error, and warning. I'm going to just copy this line and paste it

here. Let's see the arguments we have here and what each one means. Okay, the first one is 'options'. The document says you can go here

and see the difference. The option we are going to use is one because we need silent saving. So I'm going to just put one here, and

for the error and warning, because I don't want to bring up any error messages, I'm going to just put 0 and 0. Okay, I'm

going to run my script, then connect SolidWorks to Python, and then I'm going to run this

line of code. You can see here we face an error. This error says that we have a type mismatch in our second argument.

The second argument is this one. So I'm going to open help, and the second argument is an error, and I'm

going to see the type of this argument, and it is an integer. It's an integer type. It gets some error, but we don't know why.

This is because of some type mismatch between Visual Basic and Python. When we want to translate our kind of type of

variables, we need to send our value from Python to Visual Basic, and there are some mismatches. To solve this problem,

you need to create a variable manually. So you need to get access to some files, to look at this save function and find

out what type of argument it is using. So for that, you need the path for the user, my name. And here you need to

check hidden items. Here you need to go to local...sorry, the data is hidden...hidden P...site.

packages. Going to search and make...to open...you need to open a window for you here. You can see

the list. You're going to search for S...S work...S type library using version...select this one, select it, and the program is going to

generate an F for me. You can go to this, open it, or you can just hold Ctrl+click this address to open the file. This

file contains all of the functions related to Py or MA. You can see here a lot of functions for,

example, create VB DB and other functions. I'm going to search for 'save' to show you I had a problem with

save because I have a type mismatch. So I'm going to search for 'save,' and here you have information, but we are going to cover

input arguments. This is the variable type in Python, and we had a problem with the second argument. So this

is the first argument, and this is the second argument. Why I'm saying we had a problem with the second

argument here in the it says we have a type mismatch in the second argument or two or second

argument, so we have a problem with the second argument. I'm going to find the second argument, which is this member of

to, going to just copy this and paste it here. Okay, now we should be able to translate or create

create a variant. We are [music] equivalent and copy the first

member and paste it here. And for the second member, I'm going to put zero. The first argument to variant is the type of the

object to create, and the second argument is the initial content. So it means the first one is a type we don't have in

Python, so copy from here to there, and the second one is the parameter we need to pass. So we want to pass z; put

z. Going to just run this block of code and put 'arum1' here and run this another time

and have another type. So to and find out that the third one is like the second one, so I'm going to just

put argument one here, two, and now able to run this block of code and expect it to run without any problem.

contrary, and you can see so we had a problem with creating a variant, and unfortunately, sometimes you

face this problem and you need to go and find, make it run, and create this or generate this and look for your

function as I did for save and find out this to, sorry, and find the to and create some

arguments manually. Okay, guys, this is the end of this video. In summary, we talked about fancy arguments and I showed you

how to create fancy arguments manually, and you can solve this problem when you face a type mismatch by creating some arguments

manually using .com, and you can just copy this file and save it in your, I don't know, local disk. And whenever you face some problem, you can open it and look for the function you're using and solve the

problem as quickly as possible. Okay, guys, see you in the next video, and goodbye.

problem as quickly as possible. Okay guys, see you in next videos and good by

SolidWorks scripting with Python 03 - Fancy arguments

SolidWorks scripting with Python 03 - Fancy arguments