User forums > Using Code::Blocks

Too slow cursor moving (Linux)

(1/3) > >>

xintrea:
Hi all!

I install Code::Blocks v.4503 under Ubuntu 7.04. This IDE very nice, but i don`t work with this. Reason - too slow cursor moving in editor. I have P 2.2 Mhz processor, and cursor newer brake even in Java application. But in codeblocks cursor moving very slow.

If push cursor key (lefr/right), then cursor jumping a few symbol (or 3-5 line if push up/down).

If fast tying any word, then (about half-second) see as show letters in editor.

If selected text with key or mouse, this select area "lashing" to many lines, and then necessary corrected select area in low speed.

This is serious obstacle for use this IDE.


I try turn off folding and syntax highliting (syntax highliting C/C++ lang i turn off with change filemask string in setting from "*.c,*.cpp,*.cc,*.cxx,*.h,*.hpp,*.hh,*.hxx,*.inl" to "*.ijk"). But cursor moving already slow. In program top, i see 60-80% use processor time if moving cursor in Code::Blocks.

How accelerate cursor running?

dmoore:
this is a known wxWidgets issue that affects some but not all linux installs.

see

http://forums.codeblocks.org/index.php/topic,6538.0.html
http://forums.codeblocks.org/index.php/topic,2869.0.html

eranif:

--- Quote ---this is a known wxWidgets issue that affects some but not all linux installs.
--- End quote ---
I really disagree with you on this one.
IMO, it has nothing to do with wxWidgets, but to the specific machine/C::B code.
I am running C::B on the Ubuntu as well (7.04) works nice, along with other applications that are using wxWidgets + wxScintilla all are running fine.

Eran

dmoore:

--- Quote from: eranif on October 24, 2007, 08:17:22 pm ---
--- Quote ---this is a known wxWidgets issue that affects some but not all linux installs.
--- End quote ---
I really disagree with you on this one.
IMO, it has nothing to do with wxWidgets, but to the specific machine/C::B code.
I am running C::B on the Ubuntu as well (7.04) works nice, along with other applications that are using wxWidgets + wxScintilla all are running fine.

--- End quote ---

the fact that you have C::B running fine on Ubuntu does not prove the claim that this is not a wxWidgets issue. As I said in the first post, the issue only seems to affect some installations.

I'm kinda surprised that you would be disagree so strongly Eran, given that you participated in both of those threads


--- Quote from: rotalever on July 27, 2007, 12:03:02 pm ---Ok, the problem has nothing todo with CB. I tested some examples from the wxwidget webpage. The HTML-Viewer and the textboxwidget are very slow, too. It is the same lag as in CB if you try to select some text.

Compiling wxwidgets on my own doesnt change anything.

--- End quote ---


--- Quote from: rotalever on July 31, 2007, 08:13:12 pm ---... I asked this in the wxWidgets forums and someone said:
"I don't think anyone knows why, but wx apps using gtk2 do take a long time to render. There's no 'quick' fix for this. "

--- End quote ---

even you said


--- Quote from: eranif on September 24, 2006, 10:42:19 am ---I forgot to post it, but I already solved my problem. My problem was excessive calling to TextWidth() function which caused huge performance degradation.
 
This slowed the typing in the editor only Linux machines ( I tried it on FC4/5 and Ubuntu) but did not cause any slow effects on windows.

--- End quote ---

if seemingly innocuous wxWidgets functions run at wildly different speeds depending on OS, I call that an issue... (not that it is necessarily the specific problem in this particular case)

eranif:

--- Quote ---My problem was excessive calling to TextWidth() function which caused huge performance degradation.
--- End quote ---
TextWidth was not the underlying problem, but functions inside cairo caused it (AFAIR, it is font calculation function) . TextWidth is just a wrapper on top of it.

My original problem was, that I was using an editor which increased its left margin width dynamically (it called TextWidth() to calculate the margin width after every type, dont ask me why  :D).

Using '-pg' with 'g++' followed by running gprof pin pointed me to the problem. Eliminating this width calculation, restored the editing to normal / fast mode.

I never claimed it is wx problem for my case.
I do suggest that the OP should try and install another wx based editor on its machine and compare the editing speed.

Eran

Navigation

[0] Message Index

[#] Next page