Just a suggestion on the following code:

'--Parses Paths using FSO & echoes back
msgbox "Absolute path: " & objFSO.GetAbsolutePathName(objFile)
msgbox "Parent folder: " & objFSO.GetParentFolderName(objFile)
msgbox "File name: " & objFSO.GetFileName(objFile)
msgbox "Base name: " & objFSO.GetBaseName(objFile)
msgbox "Extension name: " & objFSO.GetExtensionName(objFile)
msgbox "Path to Icon: " & oShellLink.IconLocation

When i make a "TEST" object i always send the output to:
object.text

The reason for not wanting to use msgbox is that it can get into loops at places, and really mess you up.

My suggestion for the above code:

'--Parses Paths using FSO & echoes back
object.text = "Absolute path: " & objFSO.GetAbsolutePathName(objFile)
object.text = object.text & vbnewline & msgbox "Parent folder: " & objFSO.GetParentFolderName(objFile)
object.text = object.text & vbnewline & "File name: " & objFSO.GetFileName(objFile)
object.text = object.text & vbnewline & "Base name: " & objFSO.GetBaseName(objFile)
object.text = object.text & vbnewline & "Extension name: " & objFSO.GetExtensionName(objFile)
object.text = object.text & vbnewline & "Path to Icon: " & oShellLink.IconLocation

This gives you one text string with all the info above. the vbnewline just puts a line break in there.

Just my ideas. Take 'em or leave 'em

That makes perfect sense. Really I should be using msgbox constants then that would eliminate potential looping issues. I like your idea better because it is more for a demo purpose anyway. Thanks.

no problem.

You should see my desktop, its a mess of test text objects, each running its own script trying to find different things.

I like it cause i can leave them all out there, different colors, fonts, sizes, just to see what works.

I use a lot of TEST text objects when im debugging code, make test1.text test2.text etc.. and put them on the desktop and pass things like "made it this far, var1=.." so i can see what DX is doing.

Quick Q,
I love the formatting above, how did you do that in html?

There is a button on the toolbar with two brackets and text between them.
Click that box and choose your format.  Paste your code in between
Like this:

verrry nice Zu.. thanks.

Yeah, things do tend to get a little messy when you get going on a project. I added an addin folder under my object development folder which has helped considerably.

I'm tracking some of my projects from start to finish using Todolist which has lead to another object idea of plotting projects to the desktop using the bar charts. Funny how that happens.

Just a note on the code tags when you go to edit it, your code still gets screwed up but usually I'm posting from the object so, it's an easy work-a-round.

yea, Evil Msgbox Loop of Doom!

why isnt there a CTRL+C to kill the script?


I have lost more code that way, its why i HATE using them now, i put things into text objects, so that even if there is a loop, who the heck cares. I can still STOP the script.

I had spent close to 3 hrs on a gadget, it was doing something stupid "somewhere" so i put in a "msgbox stringhere" into the place where i wanted to see the stringhere var, well crap, it was in the middle of a 100 ms loop.. in about 3 seconds i had 300 msgbox windows all over my screen. NOT GOOD!!

So.. no more msgbox! LOL

I think I've got the answer to that somewhere in my script library. It halts the script until the message box is dealt with. ie. ok/close/cancel,etc.

yeah you can do that..
but its result = MsgBox(prompt[, buttons][, title][, helpfile, context])

But when you just want something to show up on the screen as feedback.. thats how you get in trouble.

but that is a good idea.

This is a very nice script. I see what you meant about the icon location. Some work some don't. I'll definitely put this in the updated version of the script helper.


Oh, yeah and it's...



No worries, though. Thanks again, SirS.

Oops! Sorry about that. Guess I should read people's profiles instead of just looking at their galleries.