I think the "Per Session" was dealing with the...
"Models In The Assembly Have Changed."
...Dialog, which is just a stupid notification, and should have never been created...
(It's in my "Duh!" List of annoying dialog boxes)
...which can only be turned off "Per Session"
The drawing/model...
I'm not sure if the BlackIce RDK can access the pc3 files...
I'll check into it though...
When dealing with computers, there are 10 things you need to know: one, zero, and the rest is Binary.
-Josh S
Ooops... Looks like you posted before I could finish typing ;-)
(There were not any replys when I started...)
Oh well...
Nice link though, I will give you a Star for the link (now bookmared ;-)) and for your effort.
Thanks,
Josh
When dealing with computers, there are 10 things you need to...
Nevermind...
You set the Template to None then Back to the Template...
Sub main()
Dim S As Sheet, SP() As Double, ST As String
With Application.SldWorks
Set S = .ActiveDoc.GetCurrentSheet
SP = S.GetProperties
ST = S.GetTemplateName
.ActiveDoc.SetupSheet4 S.GetName, SP(0)...
We have several revisions of our Title block...
The new versions are saved over the old ones with the same name and location...
To manually update them... you go to the sheet properties and click Reload in the Sheet Format/Size frame...
I recorded a macro... but it (and what I tried to derive...
And for the Name without extention...
Sub main()
Dim FullName As String, FileName As String, FilePath As String
Dim FileExt As String, DrawName As String
With Application.SldWorks.ActiveDoc
FullName = .GetPathName
FileName = Split(FullName, "\")(UBound(Split(FullName, "\")))...
Here is a fancy way... ;-)
Throgh this in a macro and run it...
Sub main()
Dim FullName As String, FileName As String, FilePath As String
With Application.SldWorks
FullName = .ActiveDoc.GetPathName
FileName = Split(FullName, "\")(UBound(Split(FullName, "\")))
FilePath =...
I am using BlackIce to generate TIFS from Named Views in a drawing...
BlackIce (by default) sets the filenames to strings of incrementing letters...
AA8.tif ... AA9.tif ... AAA.tif ... AAB.tif ... AAC.tif ...etc...
Which you then have to go through and rename them...
Using the BlackIce...
rgrayclamps,
No problem... and no idea... ;-)
For VB, any beginner VB book will do, they basically all say the same thing... (try SAM'S learn VB in 21 days)
For SW API, I learned through the following:
Recording MACROS in SW...
The API help doc (SW Menu: Help>SolidWorks API ... Help...
Hi, rgrayclamps:
COM References... (See ABOVE)
In the menu Click Project>Add Reference...
Click the COM tab
Then select SldWorks XXXX Type Library
(such as: SldWorks 2004 Type Library)
When dealing with computers, there are 10 things you need to know: one, zero, and the rest is Binary.
-Josh S
First off, do you have SolidWorks AND AutoCAD?
If you only have SW, remove the AutoCAD stuff...
As far as the SW objects go...
In the menu Click Project>Add Reference...
Click the COM tab
Then select SldWorks (and AutoCAD if you have it):
mine are listed as:
SldWorks 2004 Type Library...
as far as the notes in a SW Drawing go...
you can make a reference to other values by using strings to reference them...
such as...
If your File is named "12345.123.slddrw", and you place:
$PRP:"SW-File Name"
in a note, the note will display: "12345.123"
If an assembly (12345.123.sldasm)...
GetObject is a VB function...
System.Runtime.InteropServices.Marshal.GetActiveObject is only needed in C#
and for solidworks, 1 instance is all that is allowed... so the Try/Catch is not necessary...
CreateObject will use an existing Instance if found...
AutoCAD, on the otherhand, needs the...
You can set properties and other values, such as dimensions, to notes via SW Addressing, For example:
DWG Number: $PRP:"SW-File Name"
Scale: $PRP:"SW-Sheet Scale"
Current Sheet: $PRP:"SW-Current Sheet"
Total Sheets: $PRP:"SW-Total Sheets"
Weight: "SW-Mass@@Default@partnum.SLDASM" LBS
But is...
I typically start with a simple project and build from there...
This was my first successful test interfacing with both SW and ACAD via VB.NET (as opposed to VB6 in the past)
You might find it useful, cut out what you don't need and build on what you do need...
Objects:
TextBoxes...
