darkelf wrote:

Chr0me wrote:

Tested it, it apparently works.

Thanks.

So does this feature solve the problem that was mentioned in previous posts? I await everyone else's test results while making preparations to adding this feature onto the main program.

I do not develop clothing so I will give it to a friend who does & get back to you soon.

Well, judging from what I seem to observe (kinda ironic that I don't develop stuff myself - lost interest.) I think I've rigged up a solution:

Changelog:

• Updated for Windows Vista/7 compatibility.
• Added a product only mass deletion.
• Also added a single Product ID entry to delete its file cache. (I'm pretty sure developers would know the product ID of the product they're developing so... there.)

A little description:

If you check the developer only product cache, all other checkboxes are disabled, except for the textbox below it... this is to single out product ID's to delete. If you leave it blank, it deletes all ProductID file caches. Enter a product ID and only that product ID's cache is deleted, leaving all other product ID files untouched.

I noticed that the current IMVU Client reloads the avatar's inventory whether the cache is deleted or not. So that's a problem by client design... Last I remembered, the older clients didn't seem to have this, but I could be wrong.

I hope I did it right for developers - reducing hassle of finding individual files to delete. If there's a bug or something wrong somewhere, let me know. This will be on the first post as well.

Download 1.1

Awesome work. I'm curious as to how you developed this tool. *Downloads*

D.M wrote:

Awesome work. I'm curious as to how you developed this tool. *Downloads*

Just some sound knowledge in programming and the choice of your preferred programming language.

Used Delphi for this one. (I know some C language programmers would squint about this heheheh...) back about 8 years ago, I worked with a team to develop robust multi level database network softwares for clients but that's a long gone past. I now develop scalable websites for small, medium and local corporate companies... hence my time very scarce for hobby projects like this.

darkelf wrote:

D.M wrote:

Awesome work. I'm curious as to how you developed this tool. *Downloads*

Just some sound knowledge in programming and the choice of your preferred programming language.

Used Delphi for this one. (I know some C language programmers would squint about this heheheh...) back about 8 years ago, I worked with a team to develop robust multi level database network softwares for clients but that's a long gone past. I now develop scalable websites for small, medium and local corporate companies... hence my time very scarce for hobby projects like this.

Ah, cool. Well I just wondering how you knew where the cache was for each feature of this cleaner. Got me so interested in the inner workings of this tool now.

D.M wrote:

Ah, cool. Well I just wondering how you knew where the cache was for each feature of this cleaner. Got me so interested in the inner workings of this tool now.

There are many resources available online. Google is your best friend.

darkelf wrote:

D.M wrote:

Ah, cool. Well I just wondering how you knew where the cache was for each feature of this cleaner. Got me so interested in the inner workings of this tool now.

There are many resources available online. Google is your best friend.

Yes yes, that it is. I was more looking for specifics related to your program however. Something I thought only you would know.

D.M wrote:

Yes yes, that it is. I was more looking for specifics related to your program however. Something I thought only you would know.

Well, to be more specific, the general idea is to watch for system changes, make easier solutions to what normally needs to be done on a iterative manner... and then comes the fine details like decrypting files and decoding information from it... but I haven't gone through that yet - lacking documentation, its going to be very tedious and of course - requires more coding power...

Each client requires you to isolate the system and make general to detailed comparisons as to how the system operates - whether they make any changes to the cache locations whether the old methods are deemed redundant... in the gist of things, you'll need a few client versions running and then making comparative notes on their methods and file operations.

darkelf wrote:

D.M wrote:

Yes yes, that it is. I was more looking for specifics related to your program however. Something I thought only you would know.

Well, to be more specific, the general idea is to watch for system changes, make easier solutions to what normally needs to be done on a iterative manner... and then comes the fine details like decrypting files and decoding information from it... but I haven't gone through that yet - lacking documentation, its going to be very tedious and of course - requires more coding power...

Each client requires you to isolate the system and make general to detailed comparisons as to how the system operates - whether they make any changes to the cache locations whether the old methods are deemed redundant... in the gist of things, you'll need a few client versions running and then making comparative notes on their methods and file operations.

Well if you ever need help with that, I can run quite a few clients at once. Probably at least 10. Don't know much about how to go about the rest of that though.

D.M wrote:

Well if you ever need help with that, I can run quite a few clients at once. Probably at least 10. Don't know much about how to go about the rest of that though.

Thanks for the offer... but I can manage. However, if there's something I need help with: like conducting tests, checks and/or reviewing updated versions of my utility or methods, I'll be posting my requests on the forum.