| Author |
|
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: May 26 2002 at 09:51 | IP Logged
|
|
|
Due to response times, I recently modified the sample GetWeather macro to store the result in a Global variable (GV) every hour. In the macro, I also put just the temp and humidity in another GV [Temp Str]. When I create a new macro called Tell Temp, add a TTS line that speaks the contents of the GV, and try to refresh, the error happens (count field incorrect, not enough values for host variables). At first, I thought it was due to my using Temp in the names, but, that wasn't true. It seems related to the data in the GV, although, replacing the contents with "test" still causes the error.
Any suggestions?
Thanks,
Tony
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: May 27 2002 at 13:41 | IP Logged
|
|
|
Tony,
Export and email me the associated macros. I'll take a look and see what I can tell you. Its probably not a bug, just something not being recognized properly 
Dave.
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: May 29 2002 at 11:18 | IP Logged
|
|
|
Tony,
Found the problem. It's not a problem with running your macro but a problem with ODBC escape characters and saving your macro. In your TTS macro line, if you have {TEMP STR} in the send keys field, the "{T" is interpreted as an ODBC escape code. You can either change your global variable to start with something other than "T" or change the send keys field to {}{TEMP STR}. The blank open and close brace is a dummy value designed to prevent just this problem.
Hope this helps,
Dave.
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: May 29 2002 at 23:33 | IP Logged
|
|
|
Whoa! Thanks! Added the extra braces and all is well!
I'll have to find a list of ODBC escape characters! ;-)
Tony
|
| Back to Top |
|
| |
dhoward
Admin Group
Joined: June 29 2001
Location: United States
Online Status: Offline
Posts: 4447
|
| Posted: May 30 2002 at 10:14 | IP Logged
|
|
|
I know what you mean...Another one that Im aware of off the top of my head is {d which is often used in the send keys command {delay+xx}. This seems to burn me a lot. But if you ever get that error message again, its a sure bet that is the problem.
As a side note, my solution was not optimal in your current context. As you pointed out in your email, the double braces are spoken by the text to speech engine. When plagued by the ODBC escape sequence in a Send Keys command, the double braces are appropriate. When the problem presents itself in a variable substitution such as the TTS command, just put a space in from of the GV {TEMP STR}. This will break up the escape sequence and will be ignored by the TTS (the space would not be ignored by a Send Keys command and would actually simulate the pressing of the space key).
Dave.
|
| Back to Top |
|
| |
TonyNo
Moderator Group
Joined: December 05 2001
Location: United States
Online Status: Offline
Posts: 2889
|
| Posted: May 30 2002 at 20:03 | IP Logged
|
|
|
Thanks, Dave.
Tony
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome Bug Reports
Topic: TTS Macro Line Causes Error
