- This topic has 36 replies, 15 voices, and was last updated 19 years, 6 months ago by
.
-
Posts
-
Good News
Alright this is some good news. One of our developers, Brian, was filled with a rage that burns like a 1000x suns last week and this weekend and actually dug down into the editors to figure out what is causing this problem and figured it out. We aren’t certain yet who’s fault the problem is, BUT the workaround is as follows:Workaround for Backwards Typing
The issue seems to go away IF the first thing you do when you start up MyEclipse is to make sure no editors are open (if they are, close all of them, and restart) then open up the Properties View (Window > Show View > Other > Basic > Properties) and make sure it is active or “ontop” where ever it is open. Now open up an HTML or JSP file with the Properties view still showing. Once you have done this, the interaction that was previously causing the “Backwards typing” will disappear for the remainder of your Eclipse session. The Properties view does not need to be active anymore once you have done this BUT you cannot close it.Targetted Release for Fix
We will be targetting the public 4.0 M1 release next week with a fix for the backwards typing that will no longer need the workaround given above. We appreciate all the patience and error reports and details everyone has filed that made this possible tofix.Hurray indeed! 🙂
Does this also fix any of the other outstanding JSP editor bugs (like the ‘Christmas tree’-effect)?
Does this also fix any of the other outstanding JSP editor bugs (like the ‘Christmas tree’-effect)?
Not yet, the editors will all get a big refresh in our 5.0 release.
I see. Looking forward to 5.0 then, although that really sounds far away. (or do you intend to skip all intermediate version numbers and jump straight from 4.0x to 5.0?).
I don’t know if this has any relevance, but I thought that the simularities were too striking to not let you guys know: I’m using the LaTeX ecleTex plug-in and yesterday it also suffered from the backwards typing bug in combination with broken syntax coloring. Of course, by itself this editor is totally unrelated to MyEclipse, but perhaps they share some patterns in using the Eclipse API? Maybe this helps you in tracking down the JSP bug even further.
or do you intend to skip all intermediate version numbers and jump straight from 4.0x to 5.0?).
Yes, something like that. 5.0 will definately ship before the end of the year. Perhaps as early as end of Q3.
Of course, by itself this editor is totally unrelated to MyEclipse, but perhaps they share some patterns in using the Eclipse API? Maybe this helps you in tracking down the JSP bug even further.
Actually after people reported it in phpEclipse’s editors as well, we came to the conclusion that it seems to be an issue with the base Text classes in Eclipse’s framework. However, our crack team of ninja developers already found/fixed the bug 😉
