| Author |
 Topic  |
|
|
Uniwares
Tomato Guru
Portugal
2321 Posts |
 Posted - May 07 2004 : 1:53:30 PM
|
While it is not critical to the VC source editor when the machine is maxed out (CPU), it is VERY critical to VAX. You still can edit almost normally when your machine is busy.
But, whenevery you rely on VAX to complete your typing, it does not work in this situation.
e.g.:
make you machine busy (use the tool from the W2K resource kit)
go to the source editor and type return t<ENTER>;. Under normal conditions, after the "t", VAX's auto complete would suggest "true", enter would select it.
Now, that the machine is busy, you end up with
return t
;[true ] (the completion list after the ;)
I know that this is a nasty beast, but it happend to me in other situations already, when for example the local SQL had a spike, the compiler or linker is working in the background, or the machine maxes out for any reason.
|
Edited by - Uniwares on May 07 2004 3:37:56 PM |
|
|
support
Whole Tomato Software
5566 Posts |
Posted - May 10 2004 : 8:40:58 PM
|
You are right. This is a nasty beast.
VA X lives between the IDE and you. VA X is constantly looking to see if a situation demanding attention, eg opening of a listbox as in this case, still remains. It checks, double checks and might undo what it does, eg clear a listbox or tooltip, if a situation changes. VA X does not want to block the IDE nor your keyboard.
You have found, or periodically find, cases that get by us.
We have yet to reproduce your example with "t for true" despite the 100 statements we just added to a test file.
We will review our code and look for occurrences of the problem. |
Whole Tomato Software, Inc. |
 |
|
| |
Topic |
|
|
|
Topic Locked
