Author |
Topic |
|
Codeplug
Junior Member
USA
23 Posts |
Posted - May 20 2019 : 09:17:10 AM
|
I understand "officially unsupported", but thought I'd report it anyway. Luckily for me, I rarely use the 6.0 IDE these days since I have a "VC6 toolset" MSBuild integration, which allows that toolset to be used in VS2010 to VS2019. (The product is slowly being migrated to newer toolsets as well.)
I fired up the 6.0 IDE for the first time in a while and Copy/Paste would not work - shortcuts keys or using the Edit menu. After selecting text, Edit->Copy, Edit->Paste would show disabled, indicating an empty clipboard. Disabled VA and it started working.
I recently renewed my license and installed 2324 over 2248 (I think). Just tried 2333 as well.
Doesn't really impact me, but thought I'd report it anyway.
gg
|
Graham C Greene |
Edited by - Codeplug on May 20 2019 09:21:09 AM |
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - May 20 2019 : 3:06:28 PM
|
Not officially supported, but I had a look, just in case anyone else reports this problem. Windows 7 64bit, VC6 and VA 2333.0, copy and paste is working completely normally for me here. You might want to try uninstalling and reinstalling VA, or rebooting, to see if this makes any difference.
At a guess, there is something else going on here that is a factor, perhaps some interaction with another installed program? But it's not solely a bug in VA. |
zen is the art of being at one with the two'ness |
|
|
Codeplug
Junior Member
USA
23 Posts |
Posted - May 21 2019 : 12:35:46 PM
|
It seems something is clearing/consuming the clipboard, but only after performing cut/copy operation within 6.0 IDE. If I copy something in notepad, I can paste repeatedly in 6.0. I'm doing this with a simple dsp/dsw loaded in a blank main.cpp file.
Only software changes are updating VS2017, VS2019, and VA.
I downgraded to VA 2270 and copy/paste was functional. I re-upgraded to 2333 and back to weirdness. Disable VA and back to functional.
Copy Info in VA dialog does stay in the clipboard: License: xxx VA_X.dll file version 10.9.2333.0 built 2019.05.04 Devshl.dll version 6.0.9782.0 Devedit.pkg version 6.0.9782.0 Font: Consolas 13 (pixels) Comctl32.dll version 5.82.17763.1 Windows 8 6.2 Build 9200 4 processors (x86)
It's actually Win 10 1809, build 17763.475. |
Graham C Greene |
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - May 21 2019 : 2:51:15 PM
|
Strange, clearly connected to VA version on your system.
Are you using any other pre VS2010 versions of Visual Studio? When you run the exe installer you can select to only install VA to pre-2010 versions, or only newer versions, allowing you to leave VC6 with an older version of VA, where you are not seeing this problem. I just wanted to check that this isn't going to cause problems for VS2008, for example. |
zen is the art of being at one with the two'ness |
|
|
Codeplug
Junior Member
USA
23 Posts |
Posted - May 22 2019 : 4:03:12 PM
|
I installed 2270 to pre-2010 only and that works great - thanks for the tip. VS2019 shows VA-2333 and 6.0 shows VA-2270. I have a VS2005 solution that I open rarely and that works well with 2270 as well. |
Graham C Greene |
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - May 24 2019 : 08:33:36 AM
|
Thank you for the update, I am glad this is a reasonable solution for you. It is an odd bug, but since VC6 is no longer officially supported, and it is not super easy to reproduce here, it's not something we are going to be rushing to look into. |
zen is the art of being at one with the two'ness |
|
|
|
Topic |
|