So, with X11 backend it seems OK?

Mirek

When I switched to X11 (which, by the way is the backend I am using since then, and frankly have no idea if it is still the case with GTK) everthing worked smoothly.

Hi,

My hardware is older thinkpad (X200s) with Intel U2300 processor with @1.2GHz and 4Gb RAM.

Just tried with NOGTK version of theide and it feels significantly better. Still I can sometimes type faster than the screen updates, but it happens a lot less then with GTK version. So it really seems to be related to the backend.

Honza

dolik.rce wrote on Mon, 09 November 2015 21:00

Hi,

My hardware is older thinkpad (X200s) with Intel U2300 processor with @1.2GHz and 4Gb RAM.

Just tried with NOGTK version of theide and it feels significantly better. Still I can sometimes type faster than the screen updates, but it happens a lot less then with GTK version. So it really seems to be related to the backend.

Honza

Perhaps it would be possible to test CodeEditor alone, just to isolate the possible cause? (With both backends).

Also, what is your GTK2.0 version?

mirek wrote on Tue, 10 November 2015 09:26

dolik.rce wrote on Mon, 09 November 2015 21:00

Hi,

My hardware is older thinkpad (X200s) with Intel U2300 processor with @1.2GHz and 4Gb RAM.

Just tried with NOGTK version of theide and it feels significantly better. Still I can sometimes type faster than the screen updates, but it happens a lot less then with GTK version. So it really seems to be related to the backend.

Honza

Perhaps it would be possible to test CodeEditor alone, just to isolate the possible cause? (With both backends).

Also, what is your GTK2.0 version?

I have the latest GTK2 available, version 2.24.28. There is also GTK 3.18.2 installed on my computer, but that should not be interfering in any way.

Testing with simple single window app consisting of only CodeEditor, with the same C++ file as in TheIDE didn't show anything wrong. It works pretty fast. However, I was not able to make it use C++ syntax highlighting. Any hint on which CodeEditor method should I call and how?

Honza

#include <CtrlLib/CtrlLib.h>
#include <CodeEditor/CodeEditor.h>

using namespace Upp;

GUI_APP_MAIN {
	TopWindow win;
	CodeEditor ce;
	ce.Highlight("cpp");
	ce <<= "Hello world!";
	win.Add(ce.SizePos());
	win.Sizeable().Zoomable().Run();
}

Well, this is definitely something to investigate. Sorry for not noticing myself (perhaps my machine is too fast now...).
...
It is also possible the problem is posix related, as I am now mostly working in win32...

mirek wrote on Mon, 09 November 2015 10:26

Well, this is definitely something to investigate. Sorry for not noticing myself (perhaps my machine is too fast now...).
...
It is also possible the problem is posix related, as I am now mostly working in win32...

I getting the same problem on a ~20-core Windows machine. I thought that this is a some kind of MT-problem (code doesn't scale well on many CPUs).

At some point I even wanted to profile TheIDE but ended up just using another editor instead ...

Is there some way to make theide faster? I guess it comes from the new c++ parser. Would it be possible to limit it's functionality? E.g. skip parsing standard libraries, I can easily live without that... Or scan the file only on ctrl+space, not after each key stroke. These could be optional choices, meant for people with low-end hardware like me

Identified possible issue in GTK backend - IsPainting was returning false positives, so instead of repainting single line, whole page got repainted.

Please try!