Thanks Chip:
That gives me something to work on.
Kevin Huber
On 1/14/12, Chip Orange <[email protected]> wrote:
> Hi Kevin,
>
> I didn't see anything wrong with your code ... so I tried to approach the
> same test differently.
>
> I opened up an immed window, and typed:
>
> print activeSettings.filename
>
> and got back the name of the active set file (wineyes.set)
>
> so I typed:
>
> activeSettings.save
>
> then I opened up my profile dir, sorted it by modified date, and right near
> the very top was wineyes.set, which had been modified that very minute.
>
> Don't know if this helps, but it does give you another way of trying things
> out.
>
> I guess you're hearing the proper message spoken for it being saved, but
> then something isn't right? Are you not seeing the file timestamp change,
> or the setting you had changed isn't staying changed?
>
> Chip
>
>
>> -----Original Message-----
>> From: Kevin Huber [mailto:[email protected]]
>> Sent: Friday, January 13, 2012 4:04 PM
>> To: gw-scripting
>> Subject:
>>
>> Hi:
>> In my Proofreading script, the eventhandler that I use to
>> save settings does not work as it should.
>> the code is as follows:
>> Function DialogEventHandler(dObj, dEvent, dId, dControl)
>> DialogEventHandler = False
>> if Keyboard.KeyDescriberActive then
>> silence
>> exit function
>> end if
>> Select Case dId
>>
>> Case "button_yes"
>> If dEvent = buttonClicked Then
>> activesettings.save
>> Speak mystrings("ActiveSettingsSaved")
>> DialogEventHandler = True
>> isVisible = 0
>> dObj.Close
>> Exit Function
>> End If
>>
>> Case "button_no"
>> If dEvent = buttonClicked Then
>> Speak mystrings("ActiveSettingsNotSaved")
>> DialogEventHandler = True
>> isVisible = 0
>> dObj.Close
>> Exit Function
>> End If
>>
>> End Select
>> End Function
>>
>> The problem is that the code in the "yes" case should save
>> the settings but it appears to do nothing.
>> I think that the "settings.save" command isn't working.
>> Is there a work-around for this?
>> Kevin Huber
>>
>
>
