Kevin,
One possibility is you aren't saving the set you think you are or want
to. Based on this being in your dialog proc, you have an app dialog
up. So the active settings would be the set file being used by your
app, not the underlying program. I'm not sure what ActiveSettings you
are really wanting as there isn't enough context but just a thought.
Doug
On 1/13/2012 4:04 PM, Kevin Huber wrote:
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
