Author |
Topic |
|
gencha
Junior Member
24 Posts |
Posted - Jan 28 2009 : 07:10:50 AM
|
Since I have installed VAX I am frequently unable to mark text using the mouse. Double-clicking strings works to select them. Marking using the keyboard works as well. But dragging to mark text does not work. This is especially annoying when having to mark columns of text.
This is always specific to a single file window. Closing it and re-opening it fixes the issue. |
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Jan 28 2009 : 2:22:15 PM
|
Can you please go to:
VA Options -> System Info -> Copy Info
and paste the details (from the clipboard) into your reply. This will give us the basic information about your setup.
Do you have any other IDE plugins installed? Are you running any system utilities that might be trapping the mouse? |
zen is the art of being at one with the two'ness |
|
|
gencha
Junior Member
24 Posts |
Posted - Jan 29 2009 : 10:35:07 AM
|
VA_X.dll file version 10.5.1711.0 built 2008.12.11 Licensed to: VA X: [email protected] (1-user license) Support ends 2010.01.23 DevEnv.exe version 9.0.30729.1 msenv.dll version 9.0.30729.1 Font: Courier New 13(Pixels) Comctl32.dll version 6.0.2900.5512 Windows XP 5.1 Build 2600 Service Pack 3 2 processors
Platform: Win32 Stable Includes: C:\\Program Files\\Microsoft DirectX SDK (November 2008)\\Include; E:\\Projekte\\Boost; C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\include; C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\include; C:\\Program Files\\Microsoft SDKs\\Windows\\v6.0A\\include; C:\\Program Files\\Microsoft SDKs\\Windows\\v6.0A\\include;
Other Includes:
Stable Source Directories: C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\src\\mfc; C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\src\\mfcm; C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\src\\atl; C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\crt\\src;
The only Add-In installed besides VAX is Remotesoft .NET Explorer. I have disabled that now and will see if that changes anything about the issue.
If there are any processes that hook my mouse than I am not aware of them :P |
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Jan 30 2009 : 10:47:21 AM
|
There was a bug, which was fixed quite a while ago, where using Shift + Right click to show the VA shift + right click menu could cause problems with selecting text with the mouse.
So if you are encountering a similar problem it is possible something you are doing could be triggering this problem. Are you aware of any form of pattern?
I do not recognise "Remotesoft .NET Explorer" so I will be interested to hear if this is a factor or not.
|
zen is the art of being at one with the two'ness |
|
|
gencha
Junior Member
24 Posts |
Posted - Feb 02 2009 : 05:33:00 AM
|
Well, I don't know why, but at this time I am unable to re-produce the problem. It didn't happen for a few days now. But if it comes up again I'll be sure to let you know ;) |
|
|
NOPcode
Ketchup Master
USA
84 Posts |
Posted - Feb 03 2009 : 12:48:12 PM
|
This is the same problem that I've reported before. It can always be "cleared" by closing the source file and reopening it. There is still no pattern as far as I have noticed.
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Feb 03 2009 : 12:55:01 PM
|
When this occurs, instead of closing and the file, see if clicking on the tab for the file fixes the problem. Also, instead of closing, does ctrl+tab to another file and then back again, fix the problem?
Does this occur only when a file is first opened or at other times as well?
When this occurs, is the text caret visible in the file (as well as the current line highlight, if you have that enabled)? |
Edited by - sean on Feb 03 2009 12:57:26 PM |
|
|
gencha
Junior Member
24 Posts |
Posted - Feb 03 2009 : 12:59:15 PM
|
Well, I can answer the last two questions. The files always have been open for a while. And the caret is visible and I can also mark text. But only using the keyboard. The current line highlight is also visible. |
Edited by - gencha on Feb 03 2009 12:59:49 PM |
|
|
NOPcode
Ketchup Master
USA
84 Posts |
Posted - Feb 04 2009 : 10:39:04 AM
|
quote: When this occurs, instead of closing and the file, see if clicking on the tab for the file fixes the problem. Also, instead of closing, does ctrl+tab to another file and then back again, fix the problem?
Will try this when it happens. However, I can say that either clicking on the tab of another open file does NOT fix it, nor does opening another file.
quote:
Does this occur only when a file is first opened or at other times as well?
I believe that this happens to me when the file is already open, but I don't usually open a file to mark text with the cursor.
quote:
When this occurs, is the text caret visible in the file (as well as the current line highlight, if you have that enabled)?
Yes. The keyboard works as expected, it's just the mouse selection does not.
The problem/symptoms are exactly the same as reported by me and others before. Not a new problem. |
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Feb 04 2009 : 3:20:30 PM
|
quote: Originally posted by NOPcode
quote: When this occurs, instead of closing and the file, see if clicking on the tab for the file fixes the problem. Also, instead of closing, does ctrl+tab to another file and then back again, fix the problem?
Will try this when it happens. However, I can say that either clicking on the tab of another open file does NOT fix it, nor does opening another file.
I see. In that case, don't bother with the ctrl+tab test.
Do you have any other addins installed in VS?
|
|
|
NOPcode
Ketchup Master
USA
84 Posts |
Posted - Feb 04 2009 : 3:37:31 PM
|
quote: Originally posted by sean
Do you have any other addins installed in VS?
Nope. And also, when I had this problem before, I was running XPsp232bit; now I am using XPsp264bit - whole new system. So I doubt it was/is anything that was installed or hardware related. |
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Feb 09 2009 : 2:33:15 PM
|
The next time this occurs, please see if displaying the editor context menu (via right-click) restores the correct behavior. |
|
|
AdrianS
Senior Member
Canada
31 Posts |
Posted - Feb 21 2009 : 12:24:32 PM
|
I've had this problem on and off for a while. It just happened again and the right-click did fix it.
Unfortunately, I can't recreate the problem, even though I've gone back over my most recent actions.
1715 on VS2005 |
|
|
gencha
Junior Member
24 Posts |
Posted - Mar 06 2009 : 4:27:33 PM
|
I can confirm that right-clicking fixed the issue. |
|
|
BoredAtWork
Starting Member
1 Posts |
Posted - Jun 03 2009 : 12:30:50 PM
|
I am experiencing this as well. When it occurs right clicking does resolve the issue. Over time it will occur again in the same file. Here is my system info:
VA_X.dll file version 10.5.1724.0 built 2009.05.01 Licensed to: VA X: (5-user license) Support ends 2010.01.09 DevEnv.exe version 9.0.30729.1 msenv.dll version 9.0.30729.1 Font: Courier New 13(Pixels) Comctl32.dll version 6.0.2900.2982 Windows XP 5.1 Build 2600 S 4 processors (x86)
Platform: Win32 Stable Includes: C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\include; C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\include; C:\\Program Files\\Microsoft SDKs\\Windows\\v6.0A\\include; C:\\Program Files\\Microsoft SDKs\\Windows\\v6.0A\\include;
Other Includes:
Stable Source Directories: C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\src\\mfc; C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\src\\mfcm; C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\src\\atl; C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\crt\\src;
|
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Jun 05 2009 : 12:38:25 PM
|
We have made a change internally to try and fix this problem which should be included in the next build of VA:
case=16204 |
zen is the art of being at one with the two'ness |
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Jun 12 2009 : 9:05:53 PM
|
case=16204 is fixed in build 1727 (we think) |
|
|
|
Topic |
|