Community
Participate
Working Groups
Build Identifier: I20110518-2200 When I run eclipse with jdk 1.6 the collapse/expand button of trees (ie. those in package explorer and Window->Preferences) appear as win7 style as triangles that fade out if mouse is not in focus. But when running eclipse with jdk7 they are transformed into win98 old style like this: [+] / [-] buttons that never fade (frankly I prefer this way!! as the triangles-that-fade way is stupid and it's win7's fault xD) Changing Window->Preferences->General->Appearance->Theme from Win7 to Classic, doesn't change the tree visual style to windows classic (it's simply unchanged: triangles+fade), maybe there's another way. If you think this bug is due to jdk7 and since it's in beta you won't fix it, then maybe transform this into enhancement request for adding a way to switch from triangle+fade expand/collapse buttons for trees to non-fading [+] / [-] buttons. Thanks in advance. Reproducible: Always Steps to Reproduce: 1. to run eclipse with 1.6 java, supposedly use this eclipse.ini -startup plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.100.v20110502 -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile -vm C:/Program Files/Java/jdk1.6.0_25/bin/javaw.exe -vmargs -Dfile.encoding=UTF-8 -Dosgi.requiredJavaVersion=1.5 -Xms128m -Xmx512m and run it and notice the expand/collapse buttons of trees looks like this: when both mouse over and keyboard focused on tree: http://i.imgur.com/tjg4b.png when mouse is not hovering the tree(and also not keyboard focused): http://i.imgur.com/edRLf.png 2. run eclipse with jdk 7 (yeah I dig that's beta), by removing the lines from above eclipse.ini -vm C:/Program Files/Java/jdk1.6.0_25/bin/javaw.exe or if this doesn't work for you, then I guess you'll have to specify path to jdk7 here's the resulting screenie: http://i.imgur.com/lfZic.png I'll also add these in attachments I guess?!
Created attachment 196160 [details] e4 with jre6 focused
Created attachment 196161 [details] e4 with jre6 unfocused tree
Created attachment 196162 [details] e4 with jre7 tree
SWT, please advise.
This should work fine with recent versions of JDK 7. *** This bug has been marked as a duplicate of bug 327476 ***
(In reply to comment #5) > This should work fine with recent versions of JDK 7. > > *** This bug has been marked as a duplicate of bug 327476 *** the version of jdk7 this was tested with was: May 12, 2011 Build b142 unless something tricked me, let me check you are correct, i was using b123 here's what happened, when not specifying a vm for eclipse to use, it uses the default one in windows\system32 !! which happened to have remained at b123 (probably the first jdk7 I've ever installed) and on each subsequent update of jdk7 it only updated the program files javaw.exe not the system32 one therefore since system32 is first in path, eclipse used that jdk7 instead of the updated one, perhaps it's a failure on the jdk7 install here for not updating the system32 javaw.exe but then again why is there one needed there?! in host OSGi console typing `props` shows now: eclipse.vm = C:\Program Files\Java\jdk1.7.0\bin\javaw.exe java.runtime.version = 1.7.0-ea-b142 java.version = 1.7.0-ea java.vm.version = 21.0-b12 but that's when manually specifying the vm eclipse should use, in eclipse.ini like so: -startup plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.100.v20110502 -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile -vm C:\Program Files\Java\jdk1.7.0\bin\javaw.exe -vmargs -Dfile.encoding=UTF-8 -Dosgi.requiredJavaVersion=1.5 -Xms128m -Xmx512m ====== however when I don't specify that, ie. this eclipse.ini -startup plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.library plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.100.v20110502 -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile -vmargs -Dfile.encoding=UTF-8 -Dosgi.requiredJavaVersion=1.5 -Xms128m -Xmx512m then those values in OSGi console are: eclipse.vm = C:\Windows\system32\javaw.exe java.runtime.version = 1.7.0-ea-b123 java.version = 1.7.0-ea java.vm.version = 20.0-b04 note: I never uninstalled jdk7(not that I remember), I always just choose Yes when asked to reinstall it, ie. when running the setup install: jdk-7-ea-bin-b142-windows-x64-12_may_2011.exe apparently this doesn't update the system32\javaw.exe (and who knows what other related ones in same location)
further, I uninstalled jdk7 without uninstalling jre7 and it still used the same b123 javaw.exe in system32 then I uninstall jre7 too (so no java 7 should be left and it is so) and I noticed still uses javaw.exe in system32 but this time it's the java.version = 1.6.0_25 which is the jre6 I had still left uninstalled I then installed jdk7 again which also installed jre7 and lo an behold eclipse.vm = C:\Windows\system32\javaw.exe java.runtime.version = 1.7.0-ea-b142 therefore whatever their installer did, was probably not updating the jre7 part that is left in system32 thus it's always safe to uninstall all jdk7 and jre7 (or maybe just the latter?) such that the install can properly update that system32 jre7. I should probably report this somewhere (?) to be even safer it's best to use the -vm flag to tell eclipse which jvm to use for running itself
(In reply to comment #7) > I should probably report this somewhere (?) should be this one: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7046770. " It may take a day or two before your bug shows up in this external database. "
