well, my profile file is, but the WE program files are not. I do realize this issue has an easy work-around, and so isn't that important; however, I have done a lot of reading on the internet today, and there are a lot of articles discussing the differences, and the problems, with use of shellexecute under vista.
well, the work around is easy for me, maybe not so for new users to WE. -----Original Message----- From: Kevin Huber [mailto:[email protected]] Sent: Monday, April 12, 2010 9:35 AM To: [email protected] Subject: Re: how do you edit your xml files? Hi Chip: Just a hunch, is your Window-eyes Default folder in a different location than what it would have defaulted to when Window-eyes was installed? Kevin Huber On 4/10/10, Chip Orange <[email protected]> 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 <[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 >> >> > >
