GNU TeXmacs - Bugs: bug #56364, slow rendering behavior under...
You are not allowed to post comments on this tracker with your current authentication level.
bug #56364: slow rendering behavior under math-mode
Submitter: | Zhen Zhang <zarzen> | ||
Submitted: | Tue 21 May 2019 03:12:24 PM UTC | ||
Category: | Graphics editor | Priority: | 5 - Normal |
Item Group: | Error | Status: | Fixed |
Privacy: | Public | Assigned to: | mgubi |
Originator Name: | Open/Closed: | Closed | |
Release: | None | Release: | |
Fixed Release: | None | Fixed Release: | |
Keywords: |
Sat 06 Mar 2021 02:58:28 PM UTC, comment #2: |
Joris van der Hoeven <vdhoeven> |
Fri 30 Oct 2020 10:27:16 AM UTC, comment #1: Do you mean that it is the popup up menu that takes some time to be displayed when you click on this button? That might be normal, since there are a lot of symbols in this menu. At any rate, it will depend on your machine. Which OS are you running and what is the clockspeed of your processor?
|
Joris van der Hoeven <vdhoeven> |
Tue 21 May 2019 03:12:24 PM UTC, original submission:
rendering of Bold font button in math-mode is very slow.
|
Zhen Zhang <zarzen> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2021-03-06 | vdhoeven | Status | Need Info | Fixed | |
Open/Closed | Open | Closed | |||
2020-10-30 | vdhoeven | Status | None | Need Info | |
Assigned to | None | mgubi | |||
2020-10-23 | vdhoeven | Item Group | None | Error |
Powered by Savane 3.13-758e.
Corresponding source code
I agree that the 'bold' menu takes some time to be displayed (about 0.7 sec on my computer), but I don't see an easy solution to speed this up (there are really many buttons in this menu).
Anyway, I think that the delay remains in acceptable bounds, so this is not really a "bug".