I've had this annoyance for years...but it recently got really bad.
When I have a code window open (like for a form method) and I highlight a word or string of word in the program code, as soon as I CTRL+C or click the copy icon on the toolbar, VFP goes to lunch..."Not Responding"...window goes white-ish.
If I let it sit, long enough (like up to 5 minutes), it will eventually recover...until I commit the same mistake of trying to copy text to the clipboard. (Which I do in order to search for other occurrences, etc.)
I had this trouble in the past and I finally decided to try the NUKE solution and deleted the FOXUSER.DBF file. BOING! Fixed that problem! Copy works like a big dog on steriods now! Unfortunately, it also dumped all of the other 3000+ settings and things VFP keeps track of for reuse later. Things like smartcomplete where you type "do<space>" and it pops up a list of all the programs you've recently run...which I depend on a lot!
After a while, that good stuff builds back up and things are good again, but the COPY to clipboard seems to be even worse now (freezing for even longer periods.)
So, my question: Is there a way, like PACKing or deleting a certain row in the FOXUSER file, to get the COPY to clipboard to work as it should but without loosing all the good stuff VFP remembers? (like projects recently worked on, etc.)
Thanks for any guidance...heck I'll even take a LMGTFY or three if it helps!
Mike Copeland
No solution ... but I have a similar issue and have just worked around it - if I have a VFP app running and I try to use VFP itself (command window, prg editing etc) then any use of the clipboard just takes forever. Be interested to see if anyone else has the issue. The work around is to run the application on a different machine.
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Mike Copeland Sent: Friday, 26 February 2016 6:58 AM To: profoxtech@leafe.com Subject: VFP9 copy to clipboard causes VFP to 'hang' for long period
I've had this annoyance for years...but it recently got really bad.
When I have a code window open (like for a form method) and I highlight a word or string of word in the program code, as soon as I CTRL+C or click the copy icon on the toolbar, VFP goes to lunch..."Not Responding"...window goes white-ish.
If I let it sit, long enough (like up to 5 minutes), it will eventually recover...until I commit the same mistake of trying to copy text to the clipboard. (Which I do in order to search for other occurrences, etc.)
I had this trouble in the past and I finally decided to try the NUKE solution and deleted the FOXUSER.DBF file. BOING! Fixed that problem! Copy works like a big dog on steriods now! Unfortunately, it also dumped all of the other 3000+ settings and things VFP keeps track of for reuse later. Things like smartcomplete where you type "do<space>" and it pops up a list of all the programs you've recently run...which I depend on a lot!
After a while, that good stuff builds back up and things are good again, but the COPY to clipboard seems to be even worse now (freezing for even longer periods.)
So, my question: Is there a way, like PACKing or deleting a certain row in the FOXUSER file, to get the COPY to clipboard to work as it should but without loosing all the good stuff VFP remembers? (like projects recently worked on, etc.)
Thanks for any guidance...heck I'll even take a LMGTFY or three if it helps!
Mike Copeland
[excessive quoting removed by server]
Thanks, Darren, for the validation!
For clarification, this happens when no other routine is running in VFP in any instance.
Steps to reproduce: 1. Open VFP 2. Open method on form "modify class formname of c:\work\gga.vcx" 3. Highlight text, press CTRL+C 4. Locked-up city
I usually just use task manager to kill the instance of VFP, which likely leads to the corruption of the FOXUSER.DBF table...
Mike Copeland
Darren wrote:
No solution ... but I have a similar issue and have just worked around it - if I have a VFP app running and I try to use VFP itself (command window, prg editing etc) then any use of the clipboard just takes forever. Be interested to see if anyone else has the issue. The work around is to run the application on a different machine.
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Mike Copeland Sent: Friday, 26 February 2016 6:58 AM To: profoxtech@leafe.com Subject: VFP9 copy to clipboard causes VFP to 'hang' for long period
I've had this annoyance for years...but it recently got really bad.
When I have a code window open (like for a form method) and I highlight a word or string of word in the program code, as soon as I CTRL+C or click the copy icon on the toolbar, VFP goes to lunch..."Not Responding"...window goes white-ish.
If I let it sit, long enough (like up to 5 minutes), it will eventually recover...until I commit the same mistake of trying to copy text to the clipboard. (Which I do in order to search for other occurrences, etc.)
I had this trouble in the past and I finally decided to try the NUKE solution and deleted the FOXUSER.DBF file. BOING! Fixed that problem! Copy works like a big dog on steriods now! Unfortunately, it also dumped all of the other 3000+ settings and things VFP keeps track of for reuse later. Things like smartcomplete where you type "do<space>" and it pops up a list of all the programs you've recently run...which I depend on a lot!
After a while, that good stuff builds back up and things are good again, but the COPY to clipboard seems to be even worse now (freezing for even longer periods.)
So, my question: Is there a way, like PACKing or deleting a certain row in the FOXUSER file, to get the COPY to clipboard to work as it should but without loosing all the good stuff VFP remembers? (like projects recently worked on, etc.)
Thanks for any guidance...heck I'll even take a LMGTFY or three if it helps!
Mike Copeland
[excessive quoting removed by server]
Mike Copeland wrote on 2016-02-25:
I've had this annoyance for years...but it recently got really bad.
When I have a code window open (like for a form method) and I highlight a word or string of word in the program code, as soon as I CTRL+C or click the copy icon on the toolbar, VFP goes to lunch..."Not Responding"...window goes white-ish.
If I let it sit, long enough (like up to 5 minutes), it will eventually recover...until I commit the same mistake of trying to copy text to the clipboard. (Which I do in order to search for other occurrences, etc.)
I had this trouble in the past and I finally decided to try the NUKE solution and deleted the FOXUSER.DBF file. BOING! Fixed that problem! Copy works like a big dog on steriods now! Unfortunately, it also dumped all of the other 3000+ settings and things VFP keeps track of for reuse later. Things like smartcomplete where you type "do<space>" and it pops up a list of all the programs you've recently run...which I depend on a lot!
After a while, that good stuff builds back up and things are good again, but the COPY to clipboard seems to be even worse now (freezing for even longer periods.)
So, my question: Is there a way, like PACKing or deleting a certain row in the FOXUSER file, to get the COPY to clipboard to work as it should but without loosing all the good stuff VFP remembers? (like projects recently worked on, etc.)
Thanks for any guidance...heck I'll even take a LMGTFY or three if it
helps!
Mike Copeland
Mike,
You could try to clean out the FoxUser for updated < gomonth(date(), -2)
Then I'm looking at the Id field and seeing WINDSNIP. It seems to match up to places I've copied code from recently. Perhaps you can delete those Id's from the table, then pack it.
HTH, Tracy
Tracy Pearson PowerChurch Software
Tracy Pearson wrote:
Mike,
You could try to clean out the FoxUser for updated < gomonth(date(), -2)
Then I'm looking at the Id field and seeing WINDSNIP. It seems to match up to places I've copied code from recently. Perhaps you can delete those Id's from the table, then pack it.
HTH, Tracy
Tracy Pearson PowerChurch Software
Thanks, Tracy! I will try that.
I admit I've never mucked around in the FOXUSER.DBF file before...it might even be self-evident.
Mike
Tracy Pearson wrote:
Mike,
You could try to clean out the FoxUser for updated < gomonth(date(), -2)
Then I'm looking at the Id field and seeing WINDSNIP. It seems to match up to places I've copied code from recently. Perhaps you can delete those Id's from the table, then pack it.
HTH, Tracy
Tracy,
So far, so good. For anyone else interested...
I first tried putting a CONFIG.FPW file containing the line "resource=off" in the startup folder where VFP9.exe is located. Sure enough, the copy command now worked fine but VFP was brain-dead, not offering any help...like all the settings that I have grown to depend having it remember. Not a good option. So I removed the config.fpw file and everything went back to previous behavior (including the lock up on copy to clipboard.)
Next, on Win 7 Pro, I fired up VFP and used the SYS(2005) function to find the correct, actively-in-use FOXUSER file. It was in the hidden User AppData Roaming folder. c:\users\username\AppData\Roaming\Microsoft\Visual Foxpro 9 I started up VFP, and issued the command "set resource off" from the command line (otherwise the FOXUSER file is locked.) Use/Opened the table use "c:\users\username\AppData\Roaming\Microsoft\Visual Foxpro 9\foxuser.dbf" in 0 exclu Deleted all rows with ID field matching "WINDSNIP" or "SNIPLAST" (there were over 100 out of a total of 300) Packed the table. Exited VFP and restarted VFP.
Now, all my good stuff is remembered between sessions, and when I use the COPY to CLIPBOARD it doesn't lock up.
BTW, before the above 'fix' I had tried clicking the menu copy button on the toolbar, using the right-click copy option, and using CTRL+C on the keyboard....all of them produced the same problem.
Hopefully this will resolve the "COPY OUT TO LUNCH" problem.
Thanks again, Tracy!
Mike Copeland
Mike Copeland wrote on 2016-02-25:
Tracy,
So far, so good. For anyone else interested...
I first tried putting a CONFIG.FPW file containing the line "resource=off" in the startup folder where VFP9.exe is located. Sure enough, the copy command now worked fine but VFP was brain-dead, not offering any help...like all the settings that I have grown to depend having it remember. Not a good option. So I removed the config.fpw file and everything went back to previous behavior (including the lock up on copy to clipboard.)
Next, on Win 7 Pro, I fired up VFP and used the SYS(2005) function to find the correct, actively-in-use FOXUSER file. It was in the hidden User AppData Roaming folder. c:\users\username\AppData\Roaming\Microsoft\Visual Foxpro 9 I started up VFP, and issued the command "set resource off" from the command line (otherwise the FOXUSER file is locked.) Use/Opened the table use "c:\users\username\AppData\Roaming\Microsoft\Visual Foxpro 9\foxuser.dbf" in 0 exclu Deleted all rows with ID field matching "WINDSNIP" or "SNIPLAST" (there were over 100 out of a total of 300) Packed the table. Exited VFP and restarted VFP.
Now, all my good stuff is remembered between sessions, and when I use the COPY to CLIPBOARD it doesn't lock up.
BTW, before the above 'fix' I had tried clicking the menu copy button on the toolbar, using the right-click copy option, and using CTRL+C on the keyboard....all of them produced the same problem.
Hopefully this will resolve the "COPY OUT TO LUNCH" problem.
Thanks again, Tracy!
Mike Copeland
Mike,
Awesome. It's good to hear it worked for you.
Tracy Pearson PowerChurch Software
+1 - thanks Tracy !!!
-----Original Message----- From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Tracy Pearson Sent: Friday, 26 February 2016 10:29 AM To: profoxtech@leafe.com Subject: RE: VFP9 copy to clipboard causes VFP to 'hang' for long period
Mike Copeland wrote on 2016-02-25:
Tracy,
So far, so good. For anyone else interested...
I first tried putting a CONFIG.FPW file containing the line "resource=off" in the startup folder where VFP9.exe is located. Sure enough, the copy command now worked fine but VFP was brain-dead, not offering any help...like all the settings that I have grown to depend having it remember. Not a good option. So I removed the config.fpw file and everything went back to previous behavior (including the lock up on copy to clipboard.)
Next, on Win 7 Pro, I fired up VFP and used the SYS(2005) function to find the correct, actively-in-use FOXUSER file. It was in the hidden User AppData Roaming folder. c:\users\username\AppData\Roaming\Microsoft\Visual Foxpro 9 I started up VFP, and issued the command "set resource off" from the command line (otherwise the FOXUSER file is locked.) Use/Opened the table use "c:\users\username\AppData\Roaming\Microsoft\Visual Foxpro 9\foxuser.dbf" in 0 exclu Deleted all rows with ID field matching "WINDSNIP" or "SNIPLAST" (there were over 100 out of a total of 300) Packed the table. Exited VFP and restarted VFP.
Now, all my good stuff is remembered between sessions, and when I use the COPY to CLIPBOARD it doesn't lock up.
BTW, before the above 'fix' I had tried clicking the menu copy button on the toolbar, using the right-click copy option, and using CTRL+C on the keyboard....all of them produced the same problem.
Hopefully this will resolve the "COPY OUT TO LUNCH" problem.
Thanks again, Tracy!
Mike Copeland
Mike,
Awesome. It's good to hear it worked for you.
Tracy Pearson PowerChurch Software
[excessive quoting removed by server]
-
Darren -
Mike Copeland -
Tracy Pearson