Hi: If I cannot restore global settings, can I just change the program settings, for instance, when I turn SayCaps on, how do I turn it on for only the current program? Kevin Huber
On 4/4/11, Chip Orange <[email protected]> wrote: > Aaron: > > I think Kevin has a valid point: before 7.5 using refreshSets was all that > was need to restore all settings if you had changed one or more; now, it > doesn't work the same, and this won't do it (as you say, it only restores > the non-global settings). How would one accomplish restoration of all > settings? would loading default.set, then calling refreshSets do the job? > > thanks. > > Chip > > > _____ > > From: Aaron Smith [mailto:[email protected]] > Sent: Monday, April 04, 2011 10:55 AM > To: [email protected] > Subject: Re: Refreshsets() not working > > > I'm not able to duplicate any problems with RefreshSets. Note that this > method will not reset the global settings, but only those that have been > toggled to program specific. You can test this by opening Notepad, then > going into the Notepad set, and toggling the Activated verbosity option to > program specific. Then launch Immed, and execute RefreshSets. If you then to > back to the Notepad set, you'll notice that the activated verbosity's scope > has been set back to global (in other words, it as been reset). > > Aaron > > On 4/4/2011 10:12 AM, Kevin Huber wrote: > > Hi: > > In my proofreading script, I used the refreshsets() command to setting > > my proofreading settings back to the way they were when they were last > > saved. This strategy seemed to work in all the WE versions before > > 7.5, but in 7.5 it no longer works. > > Has the Refreshsets() command been removed entirely or has the syntax > changed? > > Kevin Huber > > > > > -- > > Aaron Smith > > Web Development * App Development * Product Support Specialist > > 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. >
