ok, I'll take the script you gave me, the next time it fails, and run it. I don't know though how it's different from what I do as a backup plan: I go into this same profiles dialog, and copy the dir path from the editbox which contains it, and open the run dialog and paste it in there and run it, which of course executes it just like the command in the vbscript (or at least, I think it would); that always opens the dir, so it's not windows explorer failing anyway. yep; could be specific to my pc, although my hunch is that it's specific to vista, as Ron has mentioned a lot of special work-arounds needed to get things to "run" under vista. thanks though for the info. Chip
_____ From: Aaron Smith [mailto:[email protected]] Sent: Saturday, April 10, 2010 6:58 PM To: [email protected] Subject: Re: how do you edit your xml files? We use the feature quite often in the support department to quickly and easily get people to their sets and/or scripts. Control-Backslash, Alt-F, L, Alt-O is significantly easier to walk someone through over the phone than it is to explain how to type an unfamiliar word like AppData, not to mention surrounding it with percent signs, and then talking them through navigating their folder structure until we finally get where we were going. So I've had quite a number of people use this feature, and I've never had it fail. I'm willing to bet that Raul and Mike's experience is the same. Or at least they've never said otherwise, and I know they would. I'll go one step further and tell you that I'm the one who added the button to that dialog, and the only thing is does is a ShellExecute on the same path destination that's listed in the edit box above the button. It's literally just: ShellExecute(NULL, NULL, *profilePath, NULL, *profilePath, SW_SHOWNORMAL); where profilePath is, again, the text in the edit box above the button I still contend that there's something specific to your machine that's causing problems with Explorer. It would be interesting to write a script (just VBScript, mind you -- not a Window-Eyes script) to do the same thing, and execute it when this problem arises, and see what happens. In VBScript, you could do: userProfilePath = "c:\full path to profile dir" Set shellObj = CreateObject("Shell.Application") shellObj.ShellExecute userProfilePath, "", "", "open", 1 Aaron On 4/10/2010 3:16 PM, Chip Orange wrote: thanks Kevin. What I'm getting out of this is that if there is a problem with the open profile dir command button in the profiles dialog, no one would know because I'm the only one using that way to get to my profile dir!!! Chip -----Original Message----- From: Kevin Huber [mailto:[email protected]] Sent: Saturday, April 10, 2010 10:49 AM To: [email protected] Subject: Re: how do you edit your xml files? Hi: I use Jamal's Go To Special Folder script to get to my default folder quickly. I just press the hotkey which brings up the list of "special" folders, and second from the bottom is one called "Window-eyes default folder"" I press Enter on that oe and, Voila, I am there. Kevin Huber On 4/9/10, Chip Orange <mailto:[email protected]> <[email protected]> wrote: Hi all, I'm curious: how to you go about editing your associated xml file for a script? I use the profile dialog of the WE control panel, and in there I press the command button (alt-O) which opens the directory for the profile. then, I can find and edit the xml file. trouble is, there are times when the buttons fails to open a dir for me, and I have to restart WE in order to make it work. GW can't duplicate this, and I wonder, if others were needing to do this to edit their xml files, then a few people should have run into this issue by now? So, do you have a different method of getting there, or have you hit this problem? thanks. Chip -- Aaron Smith Product Support Specialist * Web Development GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825 260-489-3671 * gwmicro.com To insure that you receive proper support, please include all past correspondence (where applicable), and any relevant information pertinent to your situation when submitting a problem report to the GW Micro Technical Support Team.
