copy thumbnails from files in directory to jpg
Hi guys. I am going to post this one here too, because the code process you posted often creates a 'squished' looking image for me. Code like what I am posting below has been posted here on the forums before, and did not entirely originate from me. I just customized a few things. This process seems to create a much better looking BMP file, that looks more closely like the preview image of the document that I see within the Windows file explorer screen when set to 'Extra Large Icons' view setting. And as you can see within the code, you can change the size of the output image, if needed, but I primarily just needed small images, similar to what we see in the file system previews.
AddReference "System.Drawing"
AddReference "stdole"
AddReference "System.Windows.Forms"
Class ThisRule
Sub Main
Dim oDoc As Inventor.Document = ThisDoc.Document
ConvertDocThumbnailToBMP(oDoc)
End Sub
Sub ConvertDocThumbnailToBMP(oDoc As Inventor.Document, Optional sBMPfile As String = vbNullString)
If oDoc Is Nothing Then Return
If String.IsNullOrEmpty(sBMPfile) Then
'same path and file name, but with .bmp file extension
sBMPfile = System.IO.Path.ChangeExtension(oDoc.FullFileName, ".bmp")
End If
Break
Dim oThumb As stdole.IPictureDisp
Do
oThumb = oDoc.Thumbnail
Loop While oThumb.Handle < 0
Dim oAHConverter As New AxHostConverter
Dim oImage As System.Drawing.Image = oAHConverter.GetImageFromIPictureDisp(oThumb)
'this call must be created, but is never used
Dim myCallback As New System.Drawing.Image.GetThumbnailImageAbort(AddressOf ThumbnailCallback)
'create a thumbnail before save - seems to generate a better quality
oImage.GetThumbnailImage(180, 180, myCallback, IntPtr.Zero).Save(sBMPfile, System.Drawing.Imaging.ImageFormat.Bmp)
End Sub
Public Function ThumbnailCallback() As Boolean
Return False
End Function
End Class
Class AxHostConverter
Inherits System.Windows.Forms.AxHost
Public Sub New()
'MyBase.New("{63109182-966B-4e3c-A8B2-8BC4A88D221C}")
MyBase.New((New Guid).ToString)
End Sub
Public Function GetImageFromIPictureDisp(ByVal IPDisp As stdole.IPictureDisp) As System.Drawing.Image
Return MyBase.GetPictureFromIPicture(IPDisp)
End Function
End ClassThat special 'Class' could be saved out into its own external iLogic rule, then turn its 'Straight VB Code' option on, then you could use it by referencing it in the rule using the AddVBFile line within the 'Header' of the rule, instead of directly including the whole Class block of code within the rule.
And of course, there are also several built-in Inventor API methods for saving images of the active view out to the file system with various settings, but that may require visibly opening each document, and possibly reorienting the view and zoom level (by code) before capturing the image, and that may take a longer time to process.
Wesley Crihfield
(Not an Autodesk Employee)
Thanks @yuzeaa. The images that version of your original code produces are better than the first version, and are the same physical size as the ones produces by the code I posted. However, some of the code resources it references/uses are considered to be obsolete, so I would not want to rely upon them for any future automation projects. You can read a bit more about it here:
I believe that process was originally posted online (Link) back around 2010 for use in an Inventor VBA macro, but the VBA system itself has been on its way out for years now too (Link1, Link2), and is no longer being maintained by Microsoft, so I have not been using it for anything the past few years. Here is a link to a follow-up post on the same online blog in 2012 which mentions the AxHostConverter method. Just as reference materials for others who may find this stuff later.
Wesley Crihfield
(Not an Autodesk Employee)
Hi @fichri17. If you are trying to use the code shown in Message 4, then you would have to:
- delete Lines 7 & 14.
- In Lines 9 & 13 replace the 'refdoc' variable with the 'doc' variable.
Or, you can use the code shown in Message 3, because that one just focusses on the document that was active when the rule starts, without attempting to go any deeper. Plus, as mentioned in Message 5, the code posted in Message 3 is an updated routine, while the routine being used in Message 4 is outdated. But, if it is not being relied upon for anything super important in the future, then it really does not matter which one you use, as long as it works OK for you. I know the one I posted in Message 3 is longer and more confusing looking, which does kind of suck, but that does not really matter if it is hidden behind a button, and all you are doing is clicking a button, or running a rule.
Wesley Crihfield
(Not an Autodesk Employee)
Hi @WCrihfield
Thanks for all the great help.
However, when I edited the code like you said, I get the following error -->
Any ideas ?
OK, I see it now. Any time we want to interact with the IPictureDisp Type that Inventor uses for thumbnail images, we need to include a reference to that external resource, because within that external resource is where the iPictureDisp Type is defined. If you look at my example code in Message 3, you will see the needed code in Line 2.
AddReference "stdole"Those types of lines of code (starting with AddReference or Imports) will go into the 'Header' of the iLogic rule. They help by adding recognition to those object types that are defined in external resources, and enable their related functionality. The other reference line (in Line 3) of my code in Message 3 would be necessary if you were going to be using the newer AxHostConverter route for converting the image types, as that code is doing, because the AxHost object is defined under that external resource. The System.Drawing external resource is where the Image object is defined, so adding a reference to that helps the code recognize that type of object and work with it.
Wesley Crihfield
(Not an Autodesk Employee)
Hi @fichri17. I do not currently use Vault, and have not used it in the past either, so I am simply not familiar enough with it to be able to tell you how to do that with Vault Server involved. However, I have done many other code routines that iterate though a whole folder full of files, and process specific types of Inventor files in that folder in specific ways. But I suspect that those types of codes would not be of much use without there being some sort of Vault stuff involved within the code, because the files would most likely seem like ReadOnly without the Vault related code being included when it is being used. Maybe someone else here on the forum would be able to help show you how to process a folder of files with Vault Server being involved.
Wesley Crihfield
(Not an Autodesk Employee)
