[sehlerding]

This message has not been recovered.

[Loyal Water]

This message has not been recovered.

[Riyad Kalla]

I’d also like to add if you are on the 64-bit version of Win2k3 that might explain it. We’ve seen rendering corruption of SWT-GUIs on 64-bit Win 2k3 and Vista.

[sehlerding]

Thanks for these hints. Concerning the known rendering corruption auf SWT-GUIs on 64-bit Win 2k3 I’d like to ask if there’s a chance to solve the problem. Or is the best I can do just to accept this sporacidally appearing phenomenon?

[Ton Huisman]

It will take up to Eclipse 3.4 to get this resolved, I’m seeing the same issues with all Eclipse 3.3.x based IDE’s with Vista on both 32 bit and 64 bit, where Vista 32 is almost Ok, but Vista x64 having serious issues of bad screen redraws and even missing (screen/dialog)features. Switching windows (Ctrl-F6/Ctrl-Shft-F6) sometimes relieves the repainting, but not the real faults (missing treecontrols and listviews).
Wel just have to wait for Eclipse 3.4 / MyEclipse 7.0 to have this solved.

[Riyad Kalla]

Guys, huisma13 is exactly right. The issue was in the platform SWT implementation and it has been corrected/improved in the 3.4 release which MyEclipse 7.0 will be based on. We should be getting a milestone build out in a few months for you guys to start working with so you don’t need to wait for the final GA release.

[patricktsang]

I have the exact problem when I realize it only works fine on my 32bit XP.
If the Eclipse 3.4 will solve this problem, will it provide the online upgrade from 3.3.2 to 3.4 based on MyEclipse 6.5GA?
I think we cannot wait for the other months for 7.0GA.

thanks

[Riyad Kalla]

patricktsang,
There will be no upgrade path between Eclipse 3.3 and 3.4, release increments like that introduce significant API breaks and MyEclipse cannot run ontop of 3.4, unfortunately the only solution is to wait for MyEclipse 7.0 milestones. I’m sorry.

[Author]

Posts