SW2006 creates bmp files in temp

[mncad]

Anyone noticed that SW2006 creates about 50 to 60 bitmap files in the temp folder every time it is started? I clear the temp folder on a regular basis and every time I test SW2006 the bitmaps are genereated again. The bitmaps are for icons, but I have never had this before. Just curious if anyone else has this same thing.

Thanks,
mncad

 

[SBaugh]

I have never noticed this at all.

Regards,

Scott Baugh, CSWP

http://www.scottjbaugh.com

faq731-376

 

[TateJ]

I believe the toolbox parts will do that. We already had our hardware modeled when the toolbox was unveiled. I played with it once - trying to add our hardware to it - & it generated the BMPs for the part previews in the toolbox. That's probably what's happened to you.

Windows 2000 Professional / Microsoft Intellimouse Explorer
SolidWorks 2005 SP04.0 / SpaceBall 4000 FLX
Lava Lamp​

 

[mncad]

Scott,

It is the bitmaps to create the icons for the fastening features toolbar. As soon as I start SW2006 it puts the bmps into the temp folder. It doesn't hurt anything, I had just never had that before and was wondering why I get it now.

mncad

 

[SBaugh]

Probably just something new in SW06. If you clean them out like once a week (and like you mentioned above) then ya there should not be any issues with doing this.

You could contact your VAR and have them ask SW as to why that is.

Best Regards,

Scott Baugh, CSWP

http://www.scottjbaugh.com

faq731-376

 

[TateJ]

It's a 2005 thing - or whenever the toolbox was added. But with mine - it put them in the folder where my parts were. I don't have TOOLBOX loaded anymore... But see if you can specify where the BMP files go. You don't want to wait for them to be re-created every time you clean-out your temp folders.

Windows 2000 Professional / Microsoft Intellimouse Explorer
SolidWorks 2005 SP04.0 / SpaceBall 4000 FLX
Lava Lamp​

 

[J-C]

Its the new fastening features icons added to 2006. I think it's sort of a programming thing left over from development. Sort of a bug but nothing critical. Still I would report it.

Jason

UG NX2.02.2 on Win2000 SP3
SolidWorks 2005 SP5.0 on WinXP SP2
SolidWorks 2006 SP0.0 on WinXP SP2

 

[JonathanAnderson]

The bitmap files are the icons used in SolidWorks add-ins. So any tool that loads as an add-in will create these files. This is due to the way that SolidWorks forces you to load your toolbars as an addin. There used to be a way that you could just point SW to use memory loaded by your addin dll, but now they have made that method obsolete and no longer supported. Instead you have to point SW to a bitmap file to load the toolbars for your addin, so that involves creating temporary files to do that. And of course, if SW crashes, the files get left behind. As an add-in developer, I'm kind of annoyed by it, but there's not much I can do. I think it was SW 2004 (or maybe 2005) that first allowed addins to use temporary files like this, but SW 2006 actually forces their use (or at least that's what the API documentation says).

Jonathan Anderson

 

[mncad]

The icons are from the fastening features toolbar, they are not from an add in or from tool box, I don't even have toolbox. The icons are not left behind after a crash, they are left behind every time SW2006 is started. I can clean the temp folder, start SW2006, close SW2006 and the files will be in the temp folder. I just tried and it doesn't matter if I have the toolbar active or not, it still creates all the bmps.

mncad

 

[JonathanAnderson]

Oh well. I have to deal with the addin thing as a programmer, so I figured that's what it was. I guess some of the internal SW stuff could be using the same mechanism. And if it's not cleaning up after itself even without a crash, then that's just programmers forgetting to clean up after themselves. I've done that before myself, but you would hope that things like that wouldn't be in shipped code.

Jonathan Anderson

 

[J-C]

I don't see icons for add-in's in Solidworks.

No other part of the program creates theses kind of temp icon files, I really think it's a development leftover.

Jason

UG NX2.02.2 on Win2000 SP3
SolidWorks 2005 SP5.0 on WinXP SP2
SolidWorks 2006 SP0.0 on WinXP SP2