No strong dislike either way.
It doesn't actually make it much clearer and seems like it's a rename for
its own sake.
I'll follow the convention that p2d.java goes with no matter my opinion, but
for now I'm just making it match.
On 1 September 2010 15:48, Michael Heuer heue...@gmail.com wrote:
yay
On 18 February 2010 01:44, Michael Heuer heue...@gmail.com wrote:
This is a vote for releasing Piccolo2D.Java 1.3 based on release
candidate 3 (version 1.3-rc3). Since release candidate 2 the fix
for issue 155 was rolled back and a new issue 161 has been fixed
and verified.
1.3-rc3 is
On 5 February 2010 02:34, Michael Heuer heue...@gmail.com wrote:
This is a vote for releasing Piccolo2D.Java 1.3 based on release
candidate 1 (version 1.3-rc2).
1.3-rc2 is available from the downloads page:
http://code.google.com/p/piccolo2d/downloads/list?can=2q=1.3-rc2
---
Reason for adding the component listener in PSwing's constructor was that
during the creation of unit tests for it, a bizarre situation became
obviously possible.
Invisible PSwing node and visible JComponent or Visible PSwing and invisible
JComponent.
Rather than try to parse out the behaviour
Test demonstrating the need for the callback is:
PSwingTest.testHidingComponentHidesPSwing
I believe the callback was introduced as an optimization (though it's been a
while since the change).
I will investigate further.
On 27 January 2010 22:36, cmal...@pixelzoom.com
Thanks Ben.
Funny. Would it be too geeky to say no?
I just did it to see how it might turn out and to see what other people
would build with it.
Hear hear for open source.
2010/1/12 Ben Bederson beder...@gmail.com
Wow! That is amazing. Very cool! Do you have a specific project in
mind
/javase/6/docs/api/java/awt/Container.html#invalid...
A client might call invalidatePaint() a lot of times before an actual
repaint happens.
michael
Allain Lalonde wrote:
It would seem that indeed, this behavior is intended, though I can't
see
why?
invalidatePaint() is used
Great :) No need to change anything.
2009/11/3 nls...@googlemail.com
The problem seems to be caused by updating the scene graph by a thread
other than the Swing event dispatch thread. This is not allowed, a
solution is explained in the Piccolo2D Patterns.
A consequence of updates by wrong
Good eye, invalidate paint just flags the node as needing to be
repainted. This gets picked up on the next ui cycle. I don't believe
that it will automatically bubble up the stack, though i will need to
re-read the code to confirm this. I will examine your code when i get
home to see if i can
at the end of
invalidatePaint() so that the need for repainting bubbles up to the
underlying Component.
2009/11/2 Allain Lalonde allain.lalo...@gmail.com
Good eye, invalidate paint just flags the node as needing to be
repainted. This gets picked up on the next ui cycle. I don't believe
Hey Chris!
Glad to have you aboard! What kinds of things are you planning to
build or have already built with piccolo?
If you're responsible for any of the pswing improvements, then I tip
my hat to you sir.
Look forward to working with you,
Allain Lalonde
Sent from my iPod
On Oct 30
Thank you very much for pointing that out.
It has now been fixed in the trunk.
http://code.google.com/p/piccolo2d/source/detail?r=813
2009/10/23 Nigel nigel.tamp...@f2s.com
I notice that the following line in TooltipExample.java
final PNode n =
That's great!
In regards to the solution files, I think that's fine as long as there's a
no fuss way of building it that won't scare away novice developers. If it's
does, then we might want to keep around the VS.NET 2003 project and then
just letting the IDE upgrade it on first open.
As for the
accidental, I was trying to figure out a way of unit testing the generated
path, but failed. Forgot to change it back.
2009/7/20 Michael Heuer heue...@gmail.com
On Sun, Jul 19, 2009 at 6:58 PM, codesite-nore...@google.com wrote:
Author: allain.lalonde
Date: Sun Jul 19 16:56:41 2009
New
Thanks, does text jump when zooming? On mac?
On 7/18/09, codesite-nore...@google.com codesite-nore...@google.com wrote:
Comment #16 on issue 83 by mr0...@mro.name: PSwing are fuzzy when scale!=1,
due to buffering of the PSwing
http://code.google.com/p/piccolo2d/issues/detail?id=83
great,
Agreed
On 7/18/09, codesite-nore...@google.com codesite-nore...@google.com wrote:
Comment #5 on issue 101 by mr0...@mro.name: Eliminate printStackTrace
http://code.google.com/p/piccolo2d/issues/detail?id=101
I vote against a generic, non-abstract PPiccoloException - if required we
should
Thought of another reason for doing this. Failing early would make it
easier to hunt down bugs at the source, as opposed to later when walking the
scene graph.
2009/7/17 allain allain.lalo...@gmail.com
It'd be easy enough to make it check for this at construction time and
then throw an
super.toString().replaceAll(.*\\., ) is used to strip away package names
from the default toString implementation.
2009/7/15 Samuel Robert Reid re...@colorado.edu
I don't see any advantage of the way toString is factored into a
paramString part, and I've never used paramString directly in any
18 matches
Mail list logo
