-
Notifications
You must be signed in to change notification settings - Fork 1
ChangeLog
acsmith edited this page Sep 14, 2010
·
12 revisions
-
NApplets have built-in managers: At the moment, all NApplets create their own NAppletManager by default when they’re instantiated, and store it in the
nappletManagervariable. This may or may not change down the road, depending on performance and other factors. If you declare your ownnappletManagervariable in your NApplet, that will simply supercede the default one, so (I think) everything will work fine. - NApplet nesting: NApplets can now be nested inside each other. (I need to make an example for this, though.)
-
Mousewheel support! The method
mouseWheelMoved()is called anytime the mousewheel is moved in a NApplet. The variableint mouseWheelholds the current position of the wheel, andint pmouseWheelholds the previous position of the wheel (similar tomouseX, etc.) - Translucent NApplets: The alpha value for a NApplet’s PGraphics instance will now be used when it’s pasted into its parent’s display.
-
NApplet tinting: In addition, NApplets now have a variable
color nappletTint(orint nappletTintif you’re not using the PDE) that controls how the NApplet is tinted when it’s pasted into it’s parent’s display. This can be used to apply a colored tint or a translucency to the entire NApplet. (By default, this is set to0xffffffff, i.e., fully opaque, no tint.) - Implemented the new
Nitinterface to allow for a greater variety of objects besides NApplets to be handled by the NAppletManager. (I’d like to use this architecture to implement buttons and other doodads like that, and creating a full-fledged NApplet for each would be massive overkill.) Going forward, NAppletManager will manage any and all objects that implement Nit. The NApplet class implements Nit, so this shouldn’t require any changes to existing code. - Moved test classes/applets to subpackage napplet.test.
- Fixed bug that resulted in NApplets running setup() multiple times.
- All builds will be targeted to Java 1.4.2 by default from now on, which should eliminate compatibility issues.