FAQ
Cover
\
Build
\
Source
\
Bugs
\
Reference
\
Libraries
\
Tools
The bugs database has moved
here
.
Bug 1266 : Support for smooth text in the PDE editor
Last modified: 2009-06-07 14:23
P
roject:
processing
trash
Version:
unspecified
Co
m
ponent:
android
book
core
libraries
pde
reference
tools
web
Status:
RESOLVED
Resolution:
FIXED -
Pr
i
ority:
P2
Severity:
enhancement
Platform
All
O
S:
All
Windows
Mac OS
Linux
Other
Reporter:
ajstarks
Assigned To:
fry
Attachment
Type
Created
Size
Actions
Description
: Opened: 2009-06-03 10:20
Request to support, in a standard way, if possible, antialiased text in the PDE editor.
Background:
In Processing 1.0.3, under Mac OS 10.5, support for smooth text in the PDE editor was
possible by manually editing the Info.plist file to overload the VMOptions property to pass the
-Dswing.aatext=true property.
In Processing 1.0.4 this workaround breaks (no surprise, it's a unsupported hack). I note that
in 1.0.4, the VMOptions property is now two items:
1.0.3: -Xms128M -Xmx256M
1.0.4: item1: -Xsm128M, item2: -Xmx256M
and appending -Dswing.aatext=true results in a console message:
6/3/09 11:57:37 AM [0x0-0xb80b8].org.processing.app[2142] Warning: Incorrect memory
size qualifier: M -Dswing.aatext=true Treating it as M
Is there is a preferred method for passing parameters to the VM? (run.options in
preferences.txt does not seem to work)
Additional Comment
#1 From fry 2009-06-03 12:26
sure, i'll take a look. the fix for the time being is to add another entry
like the two that are there, and the third should have the aa text
property, instead of adding it to one of the existing entries.
Additional Comment
#2 From fry 2009-06-07 14:23
fixed for 1.0.5, which honors the editor.antialias setting in
preferences.txt, rather than simply ignoring it.