The weka Wiki or SVN/Git-Repo might also list an offfical version somewhere (cannot find it right now), or you can open your weka.jar file as a zip file and extract the. If you do a google search for this file, another guy has posted his on github. #flags for loading and saving instances using DatabaseLoader/Saver # clashes between keywords and attribute names # The character to append to attribute names to avoid exceptions due to # All the reserved keywords for this database In my version of this file there is a section that looks like this. My file is different I think the actual name does not really matter, it's the filename extension that matters. The example files listed above, you need to rename it first. Weka only looks for the DatabaseUtils.props file. > java -jar /usr/share/java/weka.jar =true -Dswing.aatext=true -Dswing.aatext=trueLook inside the directory where your weka.jar file resides, and check if there exists a file called DatabaseUtils.props. > JAVA_OPTS='=true -Dswing.aatext=true -Dswing.aatext=true' jsom This has been done for both Windows and OSX versions of the runtime, but not for Linux. The Java developers need to add support for Retina/HiDPI to AWT/Swing in the same way that GTK+ and Qt needed support added. This isn't an application problem, it's a Java runtime problem. In both cases, no change in the UI was observed, which is consistent with it being a runtime, not application problem. xrender= true -Dswing.aatext=true -Dswing.aatext=true xrender= true -Dswing.aatext=true -Dswing. Using the workaround about failed to fix the problem for both JOSM and Weka, using the current versions of those applications as available in Ubuntu Wily.
Observe that the UI is unusable since all user interface elements are too small to be comfortably seen and interacted with. To recreate the issue, simply launch the applications on a computer with a high DPI (i.e. In any case, the applications affected by this for me personally include JOSM, Weka and Matlab.
0 kommentar(er)
