Community
Participate
Working Groups
Build Identifier: I20100608-0911 It seems that when a text editor uses folding ("ProjectionSupport"), StyledText.setTabstops() causes major rendering problems. If you comment out the createPartControl() method in XMLEditor.java in attachment 172935 [details] the problem goes away. Reproducible: Always Steps to Reproduce: 1. Using the plugin in attachment 172935 [details], open an XML file in "Sample XML Editor" and start typing.
Why isn't this being attended if the solution is already in the comments?
If voting was enabled (at least I can't find the "button" to '+1' this...). I'd vote this one up.
(In reply to Michael Adams from comment #2) > If voting was enabled (at least I can't find the "button" to '+1' this...). > I'd vote this one up. It's on this line in parenthesis: Importance: P3 major with 48 votes (vote) Login is required. I voted this up as well because of http://nickgravgaard.com/elastictabstops/
I too, voted this up in order to get Always Aligned as an Eclipse plugin. But this report is over 4 years old...it is not clear to me if it is still relevant, or what is required (for Mars) to fix it...Folding _does_ appear to have many cases where it "breaks" the editor in both Luna and Mars, it seems to me this fix would kill more than two birds with one stone...
(In reply to Nick Gravgaard from comment #0) > Steps to Reproduce: > 1. Using the plugin in attachment 172935 [details], open an XML file in > "Sample XML Editor" and start typing. How do I load the plugin into Eclipse? (In reply to Juan Pablo de la Torre from comment #1) > Why isn't this being attended if the solution is already in the comments? The workaround is for the text editor to drop support for code folding while the plugin is enabled.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.