beaver-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Fwd: Re: [Beaver-devel] Segfault when closing document]


From: Tobias Heinzen
Subject: [Fwd: Re: [Beaver-devel] Segfault when closing document]
Date: Fri, 20 Jun 2008 18:35:00 +0200
User-agent: Thunderbird 2.0.0.14 (X11/20080505)

and to the mailinglist also ^^
--- Begin Message --- Subject: Re: [Beaver-devel] Segfault when closing document Date: Fri, 20 Jun 2008 18:34:31 +0200 User-agent: Thunderbird 2.0.0.14 (X11/20080505)
Double 12 wrote:
Yes, the syntax highlighting gets significantly slowed down by the printing of the DEBUG_FCN messages, but without DEBUG_FCN, applying the syntax highlighting on long documents still takes a long time.

Hehe, I forgot to mention the second option. The first option was to speed up syntax highlighting. The second option is to set the Close-button as non-sensitive (not clickable) while the highlighting is still in progress.

>> My idea is to just close the windows after the syhi is done.
What do you mean exactly?
just the same as you said with setting the close-button as non-sensitive. But with my idea the close button would still be clickable but the actual closing will happen after the syhi is done (so there's a delay between clicking and the action really done).

Your XML-file and plugin ideas are great :) If we implement these things (together with upgrading to GtkUiManager), we could proudly call our next version 0.4.0. I think a basic set of commonly used languages for syntax highlighting (C/C++, Bash, Python) can be automatically loaded, though.
well they get loaded as soon as they are used. we do not know beforehand which languages the user is commonly using. the loading will take place once and if the user uses this language more often (opens more documents) then it's still loaded.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]