I recently pulled down Thor and am trying it out. On the two machines I have tried this on I get the same result. After opening the "Check for Updates" dialog, I can run updates or cancel them without a problem. Then I click on the background of _Screen. I get an error.
I have SET COVERAGE TO c:\temp\testcoverage.csv I have written an errorcatcher.prg and set the ON ERROR do errorcatcher I have opened DEBUG and set Trace Between Calls
If I type something in the Command window to throw an error, the error is caught. If I click on the white background, the error is not caught.
Does anyone have another idea on how to capture this error?
Microsoft Visual FoxPro OK Help Property 'cthordispatcher' value is too long.
I've already posted the problem in the Thor Issue tracker. Doug Hennig was not able to reproduce it.
Here's how I am able to reproduce it. Open a new session of VFP, I haven't run any code, and no Config.FPW was used. The default VFP Properties window is open. DO C:\Work\Tools\Thor\Thor\Thor\RunThor.prg Menu -> Thor -> Check for Updates Cancel Click on the background of VFP = the error.
If the Properties window is NOT open when you go through these steps it does not fail. If you are getting the error, close the Properties window and the error stops.
Now.. how to I trace this problem. Is it a problem with Thor, or is it a problem with the Properties window?
Thank you! Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:10 PM To: profoxtech@leafe.com Subject: Trying to track down why an error is occurring
I recently pulled down Thor and am trying it out. On the two machines I have tried this on I get the same result. After opening the "Check for Updates" dialog, I can run updates or cancel them without a problem. Then I click on the background of _Screen. I get an error.
I have SET COVERAGE TO c:\temp\testcoverage.csv I have written an errorcatcher.prg and set the ON ERROR do errorcatcher I have opened DEBUG and set Trace Between Calls
If I type something in the Command window to throw an error, the error is caught. If I click on the white background, the error is not caught.
Does anyone have another idea on how to capture this error?
Microsoft Visual FoxPro OK Help Property 'cthordispatcher' value is too long.
I've already posted the problem in the Thor Issue tracker. Doug Hennig was not able to reproduce it.
[excessive quoting removed by server]
Hmmm. I've not experienced this in my Thor installation. I almost always have the properties window open but it is docked outside of the main VFP window.
The cThorDispatcher property has ~8k of code in it on my system.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:18 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
Here's how I am able to reproduce it. Open a new session of VFP, I haven't run any code, and no Config.FPW was used. The default VFP Properties window is open. DO C:\Work\Tools\Thor\Thor\Thor\RunThor.prg Menu -> Thor -> Check for Updates Cancel Click on the background of VFP = the error.
If the Properties window is NOT open when you go through these steps it does not fail. If you are getting the error, close the Properties window and the error stops.
Now.. how to I trace this problem. Is it a problem with Thor, or is it a problem with the Properties window?
Thank you! Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:10 PM To: profoxtech@leafe.com Subject: Trying to track down why an error is occurring
I recently pulled down Thor and am trying it out. On the two machines I have tried this on I get the same result. After opening the "Check for Updates" dialog, I can run updates or cancel them without a problem. Then I click on the background of _Screen. I get an error.
I have SET COVERAGE TO c:\temp\testcoverage.csv I have written an errorcatcher.prg and set the ON ERROR do errorcatcher I have opened DEBUG and set Trace Between Calls
If I type something in the Command window to throw an error, the error is caught. If I click on the white background, the error is not caught.
Does anyone have another idea on how to capture this error?
Microsoft Visual FoxPro OK Help Property 'cthordispatcher' value is too long.
I've already posted the problem in the Thor Issue tracker. Doug Hennig was not able to reproduce it.
[excessive quoting removed by server]
Mine seems to be 8,319 bytes.
Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Monday, February 25, 2019 5:22 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
Hmmm. I've not experienced this in my Thor installation. I almost always have the properties window open but it is docked outside of the main VFP window.
The cThorDispatcher property has ~8k of code in it on my system.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:18 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
Here's how I am able to reproduce it. Open a new session of VFP, I haven't run any code, and no Config.FPW was used. The default VFP Properties window is open. DO C:\Work\Tools\Thor\Thor\Thor\RunThor.prg Menu -> Thor -> Check for Updates Cancel Click on the background of VFP = the error.
If the Properties window is NOT open when you go through these steps it does not fail. If you are getting the error, close the Properties window and the error stops.
Now.. how to I trace this problem. Is it a problem with Thor, or is it a problem with the Properties window?
Thank you! Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:10 PM To: profoxtech@leafe.com Subject: Trying to track down why an error is occurring
I recently pulled down Thor and am trying it out. On the two machines I have tried this on I get the same result. After opening the "Check for Updates" dialog, I can run updates or cancel them without a problem. Then I click on the background of _Screen. I get an error.
I have SET COVERAGE TO c:\temp\testcoverage.csv I have written an errorcatcher.prg and set the ON ERROR do errorcatcher I have opened DEBUG and set Trace Between Calls
If I type something in the Command window to throw an error, the error is caught. If I click on the white background, the error is not caught.
Does anyone have another idea on how to capture this error?
Microsoft Visual FoxPro OK Help Property 'cthordispatcher' value is too long.
I've already posted the problem in the Thor Issue tracker. Doug Hennig was not able to reproduce it.
[excessive quoting removed by server]
8017 for me. I can send you the text if you want to diff it.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:31 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
Mine seems to be 8,319 bytes.
Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Monday, February 25, 2019 5:22 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
Hmmm. I've not experienced this in my Thor installation. I almost always have the properties window open but it is docked outside of the main VFP window.
The cThorDispatcher property has ~8k of code in it on my system.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:18 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
Here's how I am able to reproduce it. Open a new session of VFP, I haven't run any code, and no Config.FPW was used. The default VFP Properties window is open. DO C:\Work\Tools\Thor\Thor\Thor\RunThor.prg Menu -> Thor -> Check for Updates Cancel Click on the background of VFP = the error.
If the Properties window is NOT open when you go through these steps it does not fail. If you are getting the error, close the Properties window and the error stops.
Now.. how to I trace this problem. Is it a problem with Thor, or is it a problem with the Properties window?
Thank you! Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:10 PM To: profoxtech@leafe.com Subject: Trying to track down why an error is occurring
I recently pulled down Thor and am trying it out. On the two machines I have tried this on I get the same result. After opening the "Check for Updates" dialog, I can run updates or cancel them without a problem. Then I click on the background of _Screen. I get an error.
I have SET COVERAGE TO c:\temp\testcoverage.csv I have written an errorcatcher.prg and set the ON ERROR do errorcatcher I have opened DEBUG and set Trace Between Calls
If I type something in the Command window to throw an error, the error is caught. If I click on the white background, the error is not caught.
Does anyone have another idea on how to capture this error?
Microsoft Visual FoxPro OK Help Property 'cthordispatcher' value is too long.
I've already posted the problem in the Thor Issue tracker. Doug Hennig was not able to reproduce it.
[excessive quoting removed by server]
You're below that magic 8,192 number. I wonder what puts mine over the limit?
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Monday, February 25, 2019 5:37 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
8017 for me. I can send you the text if you want to diff it.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:31 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
Mine seems to be 8,319 bytes.
Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Monday, February 25, 2019 5:22 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
Hmmm. I've not experienced this in my Thor installation. I almost always have the properties window open but it is docked outside of the main VFP window.
The cThorDispatcher property has ~8k of code in it on my system.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:18 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
Here's how I am able to reproduce it. Open a new session of VFP, I haven't run any code, and no Config.FPW was used. The default VFP Properties window is open. DO C:\Work\Tools\Thor\Thor\Thor\RunThor.prg Menu -> Thor -> Check for Updates Cancel Click on the background of VFP = the error.
If the Properties window is NOT open when you go through these steps it does not fail. If you are getting the error, close the Properties window and the error stops.
Now.. how to I trace this problem. Is it a problem with Thor, or is it a problem with the Properties window?
Thank you! Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:10 PM To: profoxtech@leafe.com Subject: Trying to track down why an error is occurring
I recently pulled down Thor and am trying it out. On the two machines I have tried this on I get the same result. After opening the "Check for Updates" dialog, I can run updates or cancel them without a problem. Then I click on the background of _Screen. I get an error.
I have SET COVERAGE TO c:\temp\testcoverage.csv I have written an errorcatcher.prg and set the ON ERROR do errorcatcher I have opened DEBUG and set Trace Between Calls
If I type something in the Command window to throw an error, the error is caught. If I click on the white background, the error is not caught.
Does anyone have another idea on how to capture this error?
Microsoft Visual FoxPro OK Help Property 'cthordispatcher' value is too long.
I've already posted the problem in the Thor Issue tracker. Doug Hennig was not able to reproduce it.
[excessive quoting removed by server]
It's possible. Diffing the files may offer some clues.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:52 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
You're below that magic 8,192 number. I wonder what puts mine over the limit?
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Monday, February 25, 2019 5:37 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
8017 for me. I can send you the text if you want to diff it.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:31 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
Mine seems to be 8,319 bytes.
Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Monday, February 25, 2019 5:22 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
Hmmm. I've not experienced this in my Thor installation. I almost always have the properties window open but it is docked outside of the main VFP window.
The cThorDispatcher property has ~8k of code in it on my system.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:18 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
Here's how I am able to reproduce it. Open a new session of VFP, I haven't run any code, and no Config.FPW was used. The default VFP Properties window is open. DO C:\Work\Tools\Thor\Thor\Thor\RunThor.prg Menu -> Thor -> Check for Updates Cancel Click on the background of VFP = the error.
If the Properties window is NOT open when you go through these steps it does not fail. If you are getting the error, close the Properties window and the error stops.
Now.. how to I trace this problem. Is it a problem with Thor, or is it a problem with the Properties window?
Thank you! Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:10 PM To: profoxtech@leafe.com Subject: Trying to track down why an error is occurring
I recently pulled down Thor and am trying it out. On the two machines I have tried this on I get the same result. After opening the "Check for Updates" dialog, I can run updates or cancel them without a problem. Then I click on the background of _Screen. I get an error.
I have SET COVERAGE TO c:\temp\testcoverage.csv I have written an errorcatcher.prg and set the ON ERROR do errorcatcher I have opened DEBUG and set Trace Between Calls
If I type something in the Command window to throw an error, the error is caught. If I click on the white background, the error is not caught.
Does anyone have another idea on how to capture this error?
Microsoft Visual FoxPro OK Help Property 'cthordispatcher' value is too long.
I've already posted the problem in the Thor Issue tracker. Doug Hennig was not able to reproduce it.
[excessive quoting removed by server]
I don't have the other text. But I just uploaded mine to https://github.com/VFPX/Thor/issues/7
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Monday, February 25, 2019 5:54 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
It's possible. Diffing the files may offer some clues.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:52 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
You're below that magic 8,192 number. I wonder what puts mine over the limit?
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Monday, February 25, 2019 5:37 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
8017 for me. I can send you the text if you want to diff it.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:31 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
Mine seems to be 8,319 bytes.
Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye Sent: Monday, February 25, 2019 5:22 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
Hmmm. I've not experienced this in my Thor installation. I almost always have the properties window open but it is docked outside of the main VFP window.
The cThorDispatcher property has ~8k of code in it on my system.
--
rk
-----Original Message----- From: ProfoxTech profoxtech-bounces@leafe.com On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:18 PM To: profoxtech@leafe.com Subject: RE: Trying to track down why an error is occurring
Here's how I am able to reproduce it. Open a new session of VFP, I haven't run any code, and no Config.FPW was used. The default VFP Properties window is open. DO C:\Work\Tools\Thor\Thor\Thor\RunThor.prg Menu -> Thor -> Check for Updates Cancel Click on the background of VFP = the error.
If the Properties window is NOT open when you go through these steps it does not fail. If you are getting the error, close the Properties window and the error stops.
Now.. how to I trace this problem. Is it a problem with Thor, or is it a problem with the Properties window?
Thank you! Tracy
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Tracy Pearson Sent: Monday, February 25, 2019 5:10 PM To: profoxtech@leafe.com Subject: Trying to track down why an error is occurring
I recently pulled down Thor and am trying it out. On the two machines I have tried this on I get the same result. After opening the "Check for Updates" dialog, I can run updates or cancel them without a problem. Then I click on the background of _Screen. I get an error.
I have SET COVERAGE TO c:\temp\testcoverage.csv I have written an errorcatcher.prg and set the ON ERROR do errorcatcher I have opened DEBUG and set Trace Between Calls
If I type something in the Command window to throw an error, the error is caught. If I click on the white background, the error is not caught.
Does anyone have another idea on how to capture this error?
Microsoft Visual FoxPro OK Help Property 'cthordispatcher' value is too long.
I've already posted the problem in the Thor Issue tracker. Doug Hennig was not able to reproduce it.
[excessive quoting removed by server]
-
Richard Kaye -
Tracy Pearson