Re: email
Hey there, Sure, that is the error message that will point us exactly to the line of the app code, that obviously is generating the error. Exactly what is going on here, I have no clue, since it will take a bit of time to investigate the surrounding code of that line, to see why it causes an error. Yet, without knowing this much, it would hardly be possible for anyone to guess why the error occured, hence I and others called for this info. Now that we know what line causes the trouble, we might do one of two. Either we could investigate what is actually going on, why it happens, what to do about it; and then fix the code. Such investigation will need someone who actually uses the app, along with the Mail Client software it is working with. I am not in that category, sorry to let you know. Alternatively, we could do what another lister suggested, simply modify the app, so as to make it skip any error caused on this line of code. That is a rather quick fix, couple of extra lines of coding might suffice. Yet, it does hold a tiny risk, in that it does not solve the problem, more just works around it. If now, the actual problem sits in more of the main core of the app, it might end up popping its snoute out, a totally other place. If you are willing to run that tiny risk, likely we can have you helped out in not too long. I am currently not able to put time into this, but just wanted to let you know why we called for the info given in the error message, and what possible can be done about it. Luckily, it seems to me, you got trouble with one of the apps that were not encrypted, hence we have the actual code handy, and can get to the point of modifying it. I really hope someone have the resources to give you a hand here. David On 11/13/2019 5:23 AM, peter Chin wrote: > Hello David, > > I hope the text given below the row of dashes what you were were > asking for: > -- > Windows Live Mail.VBS-Microsoft VB Script runtime error > Line 700 column 2 > Type mismatch 'sharedobject(...)' > < > 0x800a000d >> > > > -Original Message- From: David via Talk > Sent: Monday, November 11, 2019 10:38 AM > To: peter Chin via Talk > Cc: David > Subject: Re: email > > What exactly is the error message saying? It usually will tell us what > does not work, and which line in the scripting code that failed. That > is, which step in the processing of the script that caused the error. > Unless we know that, it all will be a matter of more or less wild > guessing. > > > Now, if you happen to have the WEPM file for the script, you might want > to reinstall the app. If you have not made any user settings in the app, > if it offers such capability, I generally suggest first uninstalling the > app altogether, prior to attempting any reinstallation. Should you not > have the WEPM file, let us see if we might be able to help you out. > > > Again, wild guessing. Since it worked for you up till recently, it might > be due to some stuff going on with your computer. Try any Anti-ware you > have, like AntiSpyware or AntiVirus. Run a full scan of the system. See > if anything gets better. Sometimes I have seen certain Antiware block > files from one of the WinEyes apps, so if that is the case, > reinstallation will not help, since it only will reinstall the file that > is being blocked. In such cases, checking the blocking list in your > anti-ware might be a good idea. > > > Don't use the software in question, so sorry for not being able to give > you any further assistance here. Next time the error pops on you, would > you mind try copy it and let the list know what it says? > > > > David > > On 11/11/2019 3:18 AM, peter Chin via Talk wrote: >> Hello all, >> >> I made some mistakes in my last message so I am sending it again. >> -- >> Hello all, >> >> I use WLM as my e-mail client on a Windows 8.1 machine and WE 9.5.4. I >> had >> >> no trouble with this client until just over a month ago. Since then, I >> get a >> >> script error message after sending out an e-mail message.I get four >> choices: >> >> ignore error, stop App, edit App or restart App. I have to choose the >> last >> >> option if I want to continue using WLM. However, WLM doesn't function >> >> properly unless I either reload WE or get out of WLM and then go back >> in. >> >> >> I hope someone can suggest a remedy for this problem. For those who >> >> understand script writing (which I don't), I include a copy of the >> script >> >> which is supposed to be re-edited. >> >> >> >> ' For license information, see WindowsLiveMail License.txt which ships >> with >> >> this package. >> >> Option Explicit >> >> >> Dim myXMLFile : myXMLFile = ClientInformation.ScriptPath & >> >> "\WindowsLiveMail.xml" >> >> Dim myINIFile : myINIFile = ClientInformation.ScriptPath & >> >> "\WindowsLiveMail.ini" >> >> Dim myStrings
Re: email
Hello David,
I hope the text given below the row of dashes what you were were asking for:
--
Windows Live Mail.VBS-Microsoft VB Script runtime error
Line 700 column 2
Type mismatch 'sharedobject(...)'
<
0x800a000d
-Original Message-
From: David via Talk
Sent: Monday, November 11, 2019 10:38 AM
To: peter Chin via Talk
Cc: David
Subject: Re: email
What exactly is the error message saying? It usually will tell us what
does not work, and which line in the scripting code that failed. That
is, which step in the processing of the script that caused the error.
Unless we know that, it all will be a matter of more or less wild guessing.
Now, if you happen to have the WEPM file for the script, you might want
to reinstall the app. If you have not made any user settings in the app,
if it offers such capability, I generally suggest first uninstalling the
app altogether, prior to attempting any reinstallation. Should you not
have the WEPM file, let us see if we might be able to help you out.
Again, wild guessing. Since it worked for you up till recently, it might
be due to some stuff going on with your computer. Try any Anti-ware you
have, like AntiSpyware or AntiVirus. Run a full scan of the system. See
if anything gets better. Sometimes I have seen certain Antiware block
files from one of the WinEyes apps, so if that is the case,
reinstallation will not help, since it only will reinstall the file that
is being blocked. In such cases, checking the blocking list in your
anti-ware might be a good idea.
Don't use the software in question, so sorry for not being able to give
you any further assistance here. Next time the error pops on you, would
you mind try copy it and let the list know what it says?
David
On 11/11/2019 3:18 AM, peter Chin via Talk wrote:
Hello all,
I made some mistakes in my last message so I am sending it again.
--
Hello all,
I use WLM as my e-mail client on a Windows 8.1 machine and WE 9.5.4. I
had
no trouble with this client until just over a month ago. Since then, I
get a
script error message after sending out an e-mail message.I get four
choices:
ignore error, stop App, edit App or restart App. I have to choose the
last
option if I want to continue using WLM. However, WLM doesn't function
properly unless I either reload WE or get out of WLM and then go back in.
I hope someone can suggest a remedy for this problem. For those who
understand script writing (which I don't), I include a copy of the script
which is supposed to be re-edited.
' For license information, see WindowsLiveMail License.txt which ships
with
this package.
Option Explicit
Dim myXMLFile : myXMLFile = ClientInformation.ScriptPath &
"\WindowsLiveMail.xml"
Dim myINIFile : myINIFile = ClientInformation.ScriptPath &
"\WindowsLiveMail.ini"
Dim myStrings : Set myStrings = Strings(myXMLFile)
Dim myScriptUpdateURL : myScriptUpdateURL =
"
http://www.gwmicro.com/scripts/windows_live_mail/xml
"
Dim checkedForUpdates : checkedForUpdates = False
Dim errorReportingEnabled : errorReportingEnabled = False
Dim SO_StandardHelpDialog : Set SO_StandardHelpDialog = Nothing
Dim SO_CheckForUpdate : Set SO_CheckForUpdate = Nothing
Dim SO_ErrorReporting : Set SO_ErrorReporting = Nothing
Dim fsObj : Set fsObj = CreateObject("Scripting.FileSystemObject")
Dim messageWindow : Set messageWindow = Nothing
Dim setFileActiveEvent : setFileActiveEvent = 0
Dim lastSpoken : lastSpoken = ""
Dim blockedFocusEvent : Set blockedFocusEvent = Nothing
Dim msaaFocusEvent : msaaFocusEvent = 0
Dim myMSAAEventSource : Set myMSAAEventSource = Nothing
Dim contactHwnd : contactHwnd = 0
Dim fieldDataEvent : fieldDataEvent = 0
Dim myMoveMessageHotkey : Set myMoveMessageHotkey = Nothing
Dim myKeyDownEvent : myKeyDownEvent = 0
Dim keyProcessedDownEventForBraille : keyProcessedDownEventForBraille = 0
Dim myBrailleObj : Set myBrailleObj = Nothing
Dim firstLetterNavStr : firstLetterNavStr = ""
Dim keyPressTimer : keyPressTimer = 0
Const TIMER_AUTOCOMPLETE = 1000
Const GRAPHIC_PREFIX = "GRAPHIC_"
Class MessageWindowClass
Private toField
Private autoCompleteSelected
Private myMSAAEventSource
Private autoCompleteEntries
Private myHotkeys
Private messageWindow
Private msaaEvents
Private timers
Private startTimerProxy
Private hotkeyProxy
Private msaaEventProxy
Public Sub Class_Initialize()
' Begin
Set toField = Nothing
Set autoCompleteSelected = Nothing
Set myMSAAEventSource = MSAAEventSource
Set autoCompleteEntries = CreateObject("Scripting.Dictionary")
Set myHotkeys = CreateObject("Scripting.Dictionary")
Set msaaEvents = CreateObject("Scripting.Dictionary")
Set timers = CreateObject("Scripting.Dictionary")
Set startTimerProxy = (New SingleParameterProxyClass).In
RE: email
Hi Peter, Incidentally, what you actually pasted into your message to the list was the complete text of the app. How you got it, makes me scratch my head in puzzlement. What we would really need in order to help is the error report. This report would be generated if you press the correct button in the dialog precisely when the error dialog appears. You would then find the report in the Window-Eyes profile folder. It could be most easily found if you sort the profile folder by date, since the report is a text file having the name of the app. You find the profile folder by choosing the Explore profile folder in the File menu of the control panel. You would then just open the file in Notepad, select its contents and paste it into a message to the list. Hth, Rod Sent from Outlook for Windows -Original Message- From: Talk On Behalf Of peter Chin via Talk Sent: November 12, 2019 9:14 PM To: David via Talk Cc: peter Chin Subject: Re: email Hello Tom, I guess you are right and in the end I will have to follow his advice. I did include a copy of the error message in my last message. I pasted it below my message after the row of dashes. The error message only occurs after I have pressed Control+n for writing a new message, then Alt+s to send it. It does not occur if I reply to a message. Thanks for trying to help. -Original Message- From: Tom Kingston via Talk Sent: Tuesday, November 12, 2019 9:03 AM To: David via Talk Cc: Tom Kingston Subject: Re: email Peter, I would do as David says below. If nothing fixes it just copy and paste the error message here. If nothing else we can just stick an error check on the line and tell it to continue and ignore the message. But knowing the error might allow us to fix it even though we're not using the program and script. Regards, Tom On 11/10/2019 9:38 PM, David via Talk wrote: > What exactly is the error message saying? It usually will tell us what > does not work, and which line in the scripting code that failed. That > is, which step in the processing of the script that caused the error. > Unless we know that, it all will be a matter of more or less wild > guessing. > > > Now, if you happen to have the WEPM file for the script, you might want > to reinstall the app. If you have not made any user settings in the app, > if it offers such capability, I generally suggest first uninstalling the > app altogether, prior to attempting any reinstallation. Should you not > have the WEPM file, let us see if we might be able to help you out. > > > Again, wild guessing. Since it worked for you up till recently, it might > be due to some stuff going on with your computer. Try any Anti-ware you > have, like AntiSpyware or AntiVirus. Run a full scan of the system. See > if anything gets better. Sometimes I have seen certain Antiware block > files from one of the WinEyes apps, so if that is the case, > reinstallation will not help, since it only will reinstall the file that > is being blocked. In such cases, checking the blocking list in your > anti-ware might be a good idea. > > > Don't use the software in question, so sorry for not being able to give > you any further assistance here. Next time the error pops on you, would > you mind try copy it and let the list know what it says? > > > > David > > On 11/11/2019 3:18 AM, peter Chin via Talk wrote: >> Hello all, >> >> I made some mistakes in my last message so I am sending it again. >> -- >> Hello all, >> >> I use WLM as my e-mail client on a Windows 8.1 machine and WE 9.5.4. I >> had >> >> no trouble with this client until just over a month ago. Since then, I >> get a >> >> script error message after sending out an e-mail message.I get four >> choices: >> >> ignore error, stop App, edit App or restart App. I have to choose the >> last >> >> option if I want to continue using WLM. However, WLM doesn't function >> >> properly unless I either reload WE or get out of WLM and then go back in. >> >> >> I hope someone can suggest a remedy for this problem. For those who >> >> understand script writing (which I don't), I include a copy of the script >> >> which is supposed to be re-edited. >> >> >> >> ' For license information, see WindowsLiveMail License.txt which ships >> with >> >> this package. >> >> Option Explicit >> >> >> Dim myXMLFile : myXMLFile = ClientInformation.ScriptPath & >> >> "\WindowsLiveMail.xml" >> >> Dim myINIFile : myINIFile = ClientInformation.ScriptPath & >> >> "\WindowsLiveMail.ini" >> >> Dim myStrings : Set myStrings = Strings(myXMLFile) >> >> Dim myScriptUpdateURL : myScriptUpdateURL = >> >> " >> http://www.gwmicro.com/scripts/windows_live_mail/xml >> " >> >> Dim checkedForUpdates : checkedForUpdates = False >> >> Dim errorReportingEnabled : errorReportingEnabled = False >> >> Dim SO_StandardHelpDialog : Set SO_StandardHelpDialog = Nothing >> >> Dim SO_CheckForUpdate : Set
Re: email
Hello David,
Thanks so much for trying to help. I did include a copy of the error message
in my last message. Unfortunately, I do not know how to find out more about
the app which is giving the error message except that it appears to be some
kind of Microsoft app. The error appears a minute or so after I have
pressed alt+s to send out an e-mail.I cannot get out of it unless I choose
"Restart App". I will try my best to find out more about this error message
but I am not sure how to proceed. If I do manage to do so, I will post it
here.
Thanks anyway.
\
-Original Message-
From: David via Talk
Sent: Monday, November 11, 2019 10:38 AM
To: peter Chin via Talk
Cc: David
Subject: Re: email
What exactly is the error message saying? It usually will tell us what
does not work, and which line in the scripting code that failed. That
is, which step in the processing of the script that caused the error.
Unless we know that, it all will be a matter of more or less wild guessing.
Now, if you happen to have the WEPM file for the script, you might want
to reinstall the app. If you have not made any user settings in the app,
if it offers such capability, I generally suggest first uninstalling the
app altogether, prior to attempting any reinstallation. Should you not
have the WEPM file, let us see if we might be able to help you out.
Again, wild guessing. Since it worked for you up till recently, it might
be due to some stuff going on with your computer. Try any Anti-ware you
have, like AntiSpyware or AntiVirus. Run a full scan of the system. See
if anything gets better. Sometimes I have seen certain Antiware block
files from one of the WinEyes apps, so if that is the case,
reinstallation will not help, since it only will reinstall the file that
is being blocked. In such cases, checking the blocking list in your
anti-ware might be a good idea.
Don't use the software in question, so sorry for not being able to give
you any further assistance here. Next time the error pops on you, would
you mind try copy it and let the list know what it says?
David
On 11/11/2019 3:18 AM, peter Chin via Talk wrote:
Hello all,
I made some mistakes in my last message so I am sending it again.
--
Hello all,
I use WLM as my e-mail client on a Windows 8.1 machine and WE 9.5.4. I
had
no trouble with this client until just over a month ago. Since then, I
get a
script error message after sending out an e-mail message.I get four
choices:
ignore error, stop App, edit App or restart App. I have to choose the
last
option if I want to continue using WLM. However, WLM doesn't function
properly unless I either reload WE or get out of WLM and then go back in.
I hope someone can suggest a remedy for this problem. For those who
understand script writing (which I don't), I include a copy of the script
which is supposed to be re-edited.
' For license information, see WindowsLiveMail License.txt which ships
with
this package.
Option Explicit
Dim myXMLFile : myXMLFile = ClientInformation.ScriptPath &
"\WindowsLiveMail.xml"
Dim myINIFile : myINIFile = ClientInformation.ScriptPath &
"\WindowsLiveMail.ini"
Dim myStrings : Set myStrings = Strings(myXMLFile)
Dim myScriptUpdateURL : myScriptUpdateURL =
"
http://www.gwmicro.com/scripts/windows_live_mail/xml
"
Dim checkedForUpdates : checkedForUpdates = False
Dim errorReportingEnabled : errorReportingEnabled = False
Dim SO_StandardHelpDialog : Set SO_StandardHelpDialog = Nothing
Dim SO_CheckForUpdate : Set SO_CheckForUpdate = Nothing
Dim SO_ErrorReporting : Set SO_ErrorReporting = Nothing
Dim fsObj : Set fsObj = CreateObject("Scripting.FileSystemObject")
Dim messageWindow : Set messageWindow = Nothing
Dim setFileActiveEvent : setFileActiveEvent = 0
Dim lastSpoken : lastSpoken = ""
Dim blockedFocusEvent : Set blockedFocusEvent = Nothing
Dim msaaFocusEvent : msaaFocusEvent = 0
Dim myMSAAEventSource : Set myMSAAEventSource = Nothing
Dim contactHwnd : contactHwnd = 0
Dim fieldDataEvent : fieldDataEvent = 0
Dim myMoveMessageHotkey : Set myMoveMessageHotkey = Nothing
Dim myKeyDownEvent : myKeyDownEvent = 0
Dim keyProcessedDownEventForBraille : keyProcessedDownEventForBraille = 0
Dim myBrailleObj : Set myBrailleObj = Nothing
Dim firstLetterNavStr : firstLetterNavStr = ""
Dim keyPressTimer : keyPressTimer = 0
Const TIMER_AUTOCOMPLETE = 1000
Const GRAPHIC_PREFIX = "GRAPHIC_"
Class MessageWindowClass
Private toField
Private autoCompleteSelected
Private myMSAAEventSource
Private autoCompleteEntries
Private myHotkeys
Private messageWindow
Private msaaEvents
Private timers
Private startTimerProxy
Private hotkeyProxy
Private msaaEventProxy
Public Sub Class_Initialize()
' Begin
Set toField = Nothing
Set autoCompleteSelected = Nothing
Set myMSAAEventSource = MSAAEventSo
Re: email
Hello Net,
Thanks for your suggestion. I will try it out to see what happens.
-Original Message-
From: net bat via Talk
Sent: Monday, November 11, 2019 10:41 AM
To: Window-Eyes Discussion List
Cc: net bat
Subject: Re: email
have you tried re installing the wlm app package? or maybe doing a wlm
system
repair?
the repair is done in the program and features list. look for the essentuals
program. start a uninstall. it will open a dialog with options to uninstall
or
repair all the essentuals programs that ar installed.
-Original Message-
From: peter Chin via Talk
Sent: Sunday, November 10, 2019 6:18 PM
To: Window-Eyes Discussion List
Cc: peter Chin
Subject: email
Hello all,
I made some mistakes in my last message so I am sending it again.
--
Hello all,
I use WLM as my e-mail client on a Windows 8.1 machine and WE 9.5.4. I had
no trouble with this client until just over a month ago. Since then, I get a
script error message after sending out an e-mail message.I get four choices:
ignore error, stop App, edit App or restart App. I have to choose the last
option if I want to continue using WLM. However, WLM doesn't function
properly unless I either reload WE or get out of WLM and then go back in.
I hope someone can suggest a remedy for this problem. For those who
understand script writing (which I don't), I include a copy of the script
which is supposed to be re-edited.
' For license information, see WindowsLiveMail License.txt which ships with
this package.
Option Explicit
Dim myXMLFile : myXMLFile = ClientInformation.ScriptPath &
"+AFw-WindowsLiveMail.xml"
Dim myINIFile : myINIFile = ClientInformation.ScriptPath &
"+AFw-WindowsLiveMail.ini"
Dim myStrings : Set myStrings = Strings(myXMLFile)
Dim myScriptUpdateURL : myScriptUpdateURL =
"
http://www.gwmicro.com/scripts/windows_live_mail/xml
"
Dim checkedForUpdates : checkedForUpdates = False
Dim errorReportingEnabled : errorReportingEnabled = False
Dim SO_StandardHelpDialog : Set SO_StandardHelpDialog = Nothing
Dim SO_CheckForUpdate : Set SO_CheckForUpdate = Nothing
Dim SO_ErrorReporting : Set SO_ErrorReporting = Nothing
Dim fsObj : Set fsObj = CreateObject("Scripting.FileSystemObject")
Dim messageWindow : Set messageWindow = Nothing
Dim setFileActiveEvent : setFileActiveEvent = 0
Dim lastSpoken : lastSpoken = ""
Dim blockedFocusEvent : Set blockedFocusEvent = Nothing
Dim msaaFocusEvent : msaaFocusEvent = 0
Dim myMSAAEventSource : Set myMSAAEventSource = Nothing
Dim contactHwnd : contactHwnd = 0
Dim fieldDataEvent : fieldDataEvent = 0
Dim myMoveMessageHotkey : Set myMoveMessageHotkey = Nothing
Dim myKeyDownEvent : myKeyDownEvent = 0
Dim keyProcessedDownEventForBraille : keyProcessedDownEventForBraille = 0
Dim myBrailleObj : Set myBrailleObj = Nothing
Dim firstLetterNavStr : firstLetterNavStr = ""
Dim keyPressTimer : keyPressTimer = 0
Const TIMER_AUTOCOMPLETE = 1000
Const GRAPHIC_PREFIX = "GRAPHIC_"
Class MessageWindowClass
Private toField
Private autoCompleteSelected
Private myMSAAEventSource
Private autoCompleteEntries
Private myHotkeys
Private messageWindow
Private msaaEvents
Private timers
Private startTimerProxy
Private hotkeyProxy
Private msaaEventProxy
Public Sub Class_Initialize()
' Begin
Set toField = Nothing
Set autoCompleteSelected = Nothing
Set myMSAAEventSource = MSAAEventSource
Set autoCompleteEntries = CreateObject("Scripting.Dictionary")
Set myHotkeys = CreateObject("Scripting.Dictionary")
Set msaaEvents = CreateObject("Scripting.Dictionary")
Set timers = CreateObject("Scripting.Dictionary")
Set startTimerProxy = (New SingleParameterProxyClass).Init(Me,
"TimerProc")
Set hotkeyProxy = (New DualParameterProxyClass).Init(Me,
"HotkeyProc")
Set msaaEventProxy = (New DualParameterProxyClass).Init(Me,
"MSAAProc")
End Sub
Public Function Init(wObj, newMessage)
' Begin
Set messageWindow = wObj
RegisterHotkeys wObj
' We only need to hook events for new messages
myMSAAEventSource.Window = messageWindow
If newMessage Then
msaaEvents(msaaEvents.Count +- 1) =
ConnectEventWithParameter(myMSAAEventSource, "OnObjectFocus",
msaaEventProxy, event_OBJECT_FOCUS)
msaaEvents(msaaEvents.Count +- 1) =
ConnectEventWithParameter(myMSAAEventSource, "OnObjectStateChange",
msaaEventProxy, event_OBJECT_STATECHANGE)
Else
msaaEvents(msaaEvents.Count +- 1) =
ConnectEventWithParameter(myMSAAEventSource, "OnObjectReorder",
msaaEventProxy, event_OBJECT_REORDER)
End If
Set Init = Me
End Function
Private Sub RegisterHotkeys(wObj)
Dim i
' Begin
For i = 1 to 7
Set myHotkeys("myAlt" & i & "HotKey") =
Re: email
Hello Rod,
I suppose you are right, but old habits die hard. I guess that I will have
to make the plunge sooner or later.
Thanks.
-Original Message-
From: Rod Hutton via Talk
Sent: Monday, November 11, 2019 11:17 PM
To: Window-Eyes Discussion List
Cc: Rod Hutton
Subject: RE: email
Hi Peter,
This is the problem with continuing to use Window-Eyes when it is no longer
being supported.
In the current situation, it forces people to try to keep using Window-Eyes
by tinkering with it.
In order to tinker with it, you have to be an advanced user.
If I run into these situations, I begin by disabling the associated app, and
see if I really need it in order to use the program which the app was
written for.
If you're willing to do this, you can go ahead and try.
Hth,
Rod
Sent from Outlook for Windows
-Original Message-
From: Talk On Behalf Of peter Chin via Talk
Sent: November 10, 2019 9:18 PM
To: Window-Eyes Discussion List
Cc: peter Chin
Subject: email
Hello all,
I made some mistakes in my last message so I am sending it again.
--
Hello all,
I use WLM as my e-mail client on a Windows 8.1 machine and WE 9.5.4. I had
no trouble with this client until just over a month ago. Since then, I get a
script error message after sending out an e-mail message.I get four choices:
ignore error, stop App, edit App or restart App. I have to choose the last
option if I want to continue using WLM. However, WLM doesn't function
properly unless I either reload WE or get out of WLM and then go back in.
I hope someone can suggest a remedy for this problem. For those who
understand script writing (which I don't), I include a copy of the script
which is supposed to be re-edited.
' For license information, see WindowsLiveMail License.txt which ships with
this package.
Option Explicit
Dim myXMLFile : myXMLFile = ClientInformation.ScriptPath &
"\WindowsLiveMail.xml"
Dim myINIFile : myINIFile = ClientInformation.ScriptPath &
"\WindowsLiveMail.ini"
Dim myStrings : Set myStrings = Strings(myXMLFile)
Dim myScriptUpdateURL : myScriptUpdateURL =
"
http://www.gwmicro.com/scripts/windows_live_mail/xml
"
Dim checkedForUpdates : checkedForUpdates = False
Dim errorReportingEnabled : errorReportingEnabled = False
Dim SO_StandardHelpDialog : Set SO_StandardHelpDialog = Nothing
Dim SO_CheckForUpdate : Set SO_CheckForUpdate = Nothing
Dim SO_ErrorReporting : Set SO_ErrorReporting = Nothing
Dim fsObj : Set fsObj = CreateObject("Scripting.FileSystemObject")
Dim messageWindow : Set messageWindow = Nothing
Dim setFileActiveEvent : setFileActiveEvent = 0
Dim lastSpoken : lastSpoken = ""
Dim blockedFocusEvent : Set blockedFocusEvent = Nothing
Dim msaaFocusEvent : msaaFocusEvent = 0
Dim myMSAAEventSource : Set myMSAAEventSource = Nothing
Dim contactHwnd : contactHwnd = 0
Dim fieldDataEvent : fieldDataEvent = 0
Dim myMoveMessageHotkey : Set myMoveMessageHotkey = Nothing
Dim myKeyDownEvent : myKeyDownEvent = 0
Dim keyProcessedDownEventForBraille : keyProcessedDownEventForBraille = 0
Dim myBrailleObj : Set myBrailleObj = Nothing
Dim firstLetterNavStr : firstLetterNavStr = ""
Dim keyPressTimer : keyPressTimer = 0
Const TIMER_AUTOCOMPLETE = 1000
Const GRAPHIC_PREFIX = "GRAPHIC_"
Class MessageWindowClass
Private toField
Private autoCompleteSelected
Private myMSAAEventSource
Private autoCompleteEntries
Private myHotkeys
Private messageWindow
Private msaaEvents
Private timers
Private startTimerProxy
Private hotkeyProxy
Private msaaEventProxy
Public Sub Class_Initialize()
' Begin
Set toField = Nothing
Set autoCompleteSelected = Nothing
Set myMSAAEventSource = MSAAEventSource
Set autoCompleteEntries = CreateObject("Scripting.Dictionary")
Set myHotkeys = CreateObject("Scripting.Dictionary")
Set msaaEvents = CreateObject("Scripting.Dictionary")
Set timers = CreateObject("Scripting.Dictionary")
Set startTimerProxy = (New SingleParameterProxyClass).Init(Me,
"TimerProc")
Set hotkeyProxy = (New DualParameterProxyClass).Init(Me,
"HotkeyProc")
Set msaaEventProxy = (New DualParameterProxyClass).Init(Me,
"MSAAProc")
End Sub
Public Function Init(wObj, newMessage)
' Begin
Set messageWindow = wObj
RegisterHotkeys wObj
' We only need to hook events for new messages
myMSAAEventSource.Window = messageWindow
If newMessage Then
msaaEvents(msaaEvents.Count + 1) =
ConnectEventWithParameter(myMSAAEventSource, "OnObjectFocus",
msaaEventProxy, event_OBJECT_FOCUS)
msaaEvents(msaaEvents.Count + 1) =
ConnectEventWithParameter(myMSAAEventSource, "OnObjectStateChange",
msaaEventProxy, event_OBJECT_STATECHANGE)
Else
msaaEvents(msaaEvents.Count + 1) =
ConnectEventWithPar
Re: email
Hello Tom,
I guess you are right and in the end I will have to follow his advice. I did
include a copy of the error message in my last message. I pasted it below my
message after the row of dashes. The error message only occurs after I have
pressed Control+n for writing a new message, then Alt+s to send it. It does
not occur if I reply to a message.
Thanks for trying to help.
-Original Message-
From: Tom Kingston via Talk
Sent: Tuesday, November 12, 2019 9:03 AM
To: David via Talk
Cc: Tom Kingston
Subject: Re: email
Peter,
I would do as David says below. If nothing fixes it just copy and paste
the error message here. If nothing else we can just stick an error check
on the line and tell it to continue and ignore the message. But knowing
the error might allow us to fix it even though we're not using the
program and script.
Regards,
Tom
On 11/10/2019 9:38 PM, David via Talk wrote:
What exactly is the error message saying? It usually will tell us what
does not work, and which line in the scripting code that failed. That
is, which step in the processing of the script that caused the error.
Unless we know that, it all will be a matter of more or less wild
guessing.
Now, if you happen to have the WEPM file for the script, you might want
to reinstall the app. If you have not made any user settings in the app,
if it offers such capability, I generally suggest first uninstalling the
app altogether, prior to attempting any reinstallation. Should you not
have the WEPM file, let us see if we might be able to help you out.
Again, wild guessing. Since it worked for you up till recently, it might
be due to some stuff going on with your computer. Try any Anti-ware you
have, like AntiSpyware or AntiVirus. Run a full scan of the system. See
if anything gets better. Sometimes I have seen certain Antiware block
files from one of the WinEyes apps, so if that is the case,
reinstallation will not help, since it only will reinstall the file that
is being blocked. In such cases, checking the blocking list in your
anti-ware might be a good idea.
Don't use the software in question, so sorry for not being able to give
you any further assistance here. Next time the error pops on you, would
you mind try copy it and let the list know what it says?
David
On 11/11/2019 3:18 AM, peter Chin via Talk wrote:
Hello all,
I made some mistakes in my last message so I am sending it again.
--
Hello all,
I use WLM as my e-mail client on a Windows 8.1 machine and WE 9.5.4. I
had
no trouble with this client until just over a month ago. Since then, I
get a
script error message after sending out an e-mail message.I get four
choices:
ignore error, stop App, edit App or restart App. I have to choose the
last
option if I want to continue using WLM. However, WLM doesn't function
properly unless I either reload WE or get out of WLM and then go back in.
I hope someone can suggest a remedy for this problem. For those who
understand script writing (which I don't), I include a copy of the script
which is supposed to be re-edited.
' For license information, see WindowsLiveMail License.txt which ships
with
this package.
Option Explicit
Dim myXMLFile : myXMLFile = ClientInformation.ScriptPath &
"\WindowsLiveMail.xml"
Dim myINIFile : myINIFile = ClientInformation.ScriptPath &
"\WindowsLiveMail.ini"
Dim myStrings : Set myStrings = Strings(myXMLFile)
Dim myScriptUpdateURL : myScriptUpdateURL =
"
http://www.gwmicro.com/scripts/windows_live_mail/xml
"
Dim checkedForUpdates : checkedForUpdates = False
Dim errorReportingEnabled : errorReportingEnabled = False
Dim SO_StandardHelpDialog : Set SO_StandardHelpDialog = Nothing
Dim SO_CheckForUpdate : Set SO_CheckForUpdate = Nothing
Dim SO_ErrorReporting : Set SO_ErrorReporting = Nothing
Dim fsObj : Set fsObj = CreateObject("Scripting.FileSystemObject")
Dim messageWindow : Set messageWindow = Nothing
Dim setFileActiveEvent : setFileActiveEvent = 0
Dim lastSpoken : lastSpoken = ""
Dim blockedFocusEvent : Set blockedFocusEvent = Nothing
Dim msaaFocusEvent : msaaFocusEvent = 0
Dim myMSAAEventSource : Set myMSAAEventSource = Nothing
Dim contactHwnd : contactHwnd = 0
Dim fieldDataEvent : fieldDataEvent = 0
Dim myMoveMessageHotkey : Set myMoveMessageHotkey = Nothing
Dim myKeyDownEvent : myKeyDownEvent = 0
Dim keyProcessedDownEventForBraille : keyProcessedDownEventForBraille = 0
Dim myBrailleObj : Set myBrailleObj = Nothing
Dim firstLetterNavStr : firstLetterNavStr = ""
Dim keyPressTimer : keyPressTimer = 0
Const TIMER_AUTOCOMPLETE = 1000
Const GRAPHIC_PREFIX = "GRAPHIC_"
Class MessageWindowClass
Private toField
Private autoCompleteSelected
Private myMSAAEventSource
Private autoCompleteEntries
Private myHotkeys
Private messageWindow
Private msaaEvents
Private timers
Private startTimerProxy
Private h
