For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 9 replies, 5 voices, and was last updated 21 years, 7 months ago by
.
-
Posts
-
As I use the JSP editor in 3.7 to edit JSP/JSF files, the colors are being lost as I close and reopen files. For instance I have my prefs set so that jsp tags are in orange, (<jsp:include …>, <f:view …>). Now if I close the file and reopen it then the colors will be in the color of blue, which is what I set normal HTML to. However, if I type a new tag in the file I just opened then the new tag will be in orange, although all the old tags are still in blue.
One of the things that could happen when files are opened is that the cache of known tags is updated by reparsing. So, sometimes there’s a delay between the file opening and a proper color being assigned to tags. Could this be what you’re seeing?
I don’t think so, since there is not a delay in colors being assinged to the tags. They are simple all blue. However I have determined further that if I make a modification on a line in the file, then all tags on that line to the end of the file are then colored correctly. I can then revert the file and the whole file is properly colored. Sorry, but this little bug slipped out.
I did some more checking on this and we have an open bug report on this problem but the developer in charge reports that “I am not sure, whether this can be fixed, since the SourceViewers invalidate()
method seems broken in the M7 build.” We’ll keep after it for a future release.The JSP editor with the new ME 3.7.2 plugin doesn’t save my color preferences when I restart Eclipse 3.0M8.
And it still suffers from the same problem Binyan mentioned way at the start of this topic.
Any ideas..?
seandynan,
Strange… so you change the colors, hit Apply and then OK. Exist Eclipse, and reload it, and the colors are all default again?Thanks for the report. I replicated this behavior and submitted a problem report for it. I’m not sure what M8 is doing to preferences now. M-builds are a moving target full of new undocumented, incomplete, and broken behaviors and APIs. Supporting them makes juggling knives feel safe. 🙂
I try to research this further and see if there is a quick resolution.
@support-michael wrote:
M-builds are a moving target full of new undocumented, incomplete, and broken behaviors and APIs.
I hear you brother :(.
I’m just happy that Genuitec tries to keep up with Eclipse milestones. It is frankly astonishing that an app so close to release hasn’t had its core locked down long ago.
—
SeanThe Eclipse team is doing an awesome job with the many new features and the underlying complexity that we take for granted. For example consider how complicated all the backgrounding of tasks is and the requirements that the workspace can no longer be exclusively locked (get’s crazy fast). Complexity is definitely out there. Once E3 stablizes we plan to exploit the heck out of those new capabilities with our own new feature sets.
