Author |
Topic |
|
KirillMueller
Ketchup Master
72 Posts |
Posted - Jul 05 2004 : 11:52:02 AM
|
Hello,
sometimes, when my system is loaded and I switch to Visual Studio 6.0 with Visual Assist X enabled, it takes ages to paint the active source code window. The symbols are painted one after another with >50 ms delay. When the hard disk is not busy, painting is pretty fast. I have 1 GB RAM installed.
It seems that the routine that paints a source code window sometimes has to look up the color of a symbol from hard disk or from swapped-out memory. In my opinion, a paint handler should never use the hard disk if avoidable.
When VAX doesn't know the color of a symbol right away, it could appear in black first and be colored correctly later. Or, maybe preventing the "symbol color memory" from being swapped would help?
Regards,
Kirill |
|
Uniwares
Tomato Guru
Portugal
2322 Posts |
Posted - Jul 05 2004 : 3:25:27 PM
|
Try enabling the "Keep symbols in memory" option on the performance tab. This should solve this problem. |
|
|
KirillMueller
Ketchup Master
72 Posts |
Posted - Jul 09 2004 : 04:52:18 AM
|
This option is already on.
Furthermore, I have experienced several hangs of Visual Studio 6 SP 6 during a slow repaint (most probably by VAX).
Support? |
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Jul 09 2004 : 10:57:14 AM
|
Our coloring algorithms are built for speed -- there has been much discussion about it in the forums. Something is just broken in VA X for your setup.
If you do not have build 1244, start by installing it.
http://www.wholetomato.com/downloads
The fact there is disk activity during painting does not imply painting is the culprit. It could very well be something else.
Are your sources local?
Do you have any other add-ins installed?
Can you check the following thread? Perhaps you experience the same problem these users report.
http://forum.wholetomato.com/forum/topic.asp?TOPIC_ID=2504 |
Whole Tomato Software, Inc. |
|
|
KirillMueller
Ketchup Master
72 Posts |
Posted - Jul 11 2004 : 09:38:11 AM
|
I have the latest install, my sources are local, and I don't have other add-ins.
But: I have a script that compiles my projects at another location so I can edit the code while compiling. The script starts two other MSDEV.EXE's. I believe the reason for my problem are the other instances of MSDEV, since the problem only occurs during compilation.
Thank you. I'll move to the other thread.
Sorry for the wrong hint. "Busy hard disk" means "compilation" on my system :-) |
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Jul 11 2004 : 11:10:46 AM
|
Anyone familiar with Incredibuild? We see their banners on CodeProject and their site looks professional.
http://www.xoreax.com |
Whole Tomato Software, Inc. |
|
|
Baga
Tomato Guru
122 Posts |
Posted - Jul 12 2004 : 01:15:41 AM
|
Nice product (Incredibuild).
1. Easily make project compile in 5 min instead of 40.
2. Don't use it for production builds. Sometimes (rarely) it messes up symbols, virtual tables, etc. Fixed by full rebuild (see 1.).
3. They are greedy as ... er... your choice of curse word... |
|
|
|
Topic |
|